Carl wrote:
Not if ES is set to 1, which as a rule it should be. Just about
everything runs smoother that way.
Good point. E.g., when an XPL program does a SEarch and it is expected to
eventually get a "not found," you don't want it to beep at the user. So
then you use a s/g to trap the errors you are interested in.
How do you have the program report only those errors you want reported? A
lot of IF tests? Or is only while debugging that you use:
≪IF
Harry Binswanger
hb@xxxxxxxx