×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
I'll go with "generally" on the multiple returns. There are times when
it's just oh so much clearer. But I understand your concern. However I
do not like
eval returnvar = this;
...
eval returnvar = that;
...
eval returnvar = theotherthing;
...
return returnvar;
just to have one return statement. Harkens back to subroutines, or called
programs versus subprocedures
eval parm1=this;
eval parm2=that;
eval parm3=theotherthing;
exsr mysubr
or call myprogram
parm parm1
parm parm2
parm parm3
eval workvar=parm3;
So messy.
And on the Not, I did just rewrite my previous example to take out the Not
before I sent it because I too thought it was more readable without the
not.
Rob Berendt
This mailing list archive is Copyright 1997-2025 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact
[javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
