tracker down so will post here before i forget
the basic parser .. could it be enhanced to fail on first instance ?
if not(assinged(var)) OR var=' then
this will fail on the second part even if the first part finds it. At least that is what appears here.
Could this be enhanced to fail first test and not do second test .. ??
thanks
DSig
Dave,
I'll put this one into the Suggestion Box for future review.
Thanks,
Sean
I guess that's why most code I've seen has:
If Unassigned(var) then var='
Yeah .. it would just be nice to have
if not(assigne(a)) OR a=NULL$ then
instead of
if not(assigned(a)) then a=NULL$
if a=NULL$ then
only 1 less line .. but more in line with 20th century programming languages .. well except for mv languages which well all know barely made the 19th century
Didn't the 19th century have true optimizing compilers or was that the 18th century ?
depends if you worked in MV or not. But they did have those nice astrix across the screen .. oh technology ..
compilation complete!!