|
This is the best argument I've seen. I understand the desire to keep backward compatibility. Then again, what happened with everyone who had the field name "eval" in their programs? How big of an issue was this, really? But to stick a hyphen in every new opcode, that's just shatteringly ugly to me. I'll go with Larry's suggestion instead. Make 'em all BIFs from now on, and the percent sign rules. Joe > From: Larry Ducie > > > We could have... > > if %evalCorr(myFirstDS:mySecondDS) = true; // returns true of at least one > mapping occurs, or if the mapping completes successfully. > > or... > > if %evalCorr(myFirstDS:mySecondDS) > *zero; // returns the number of > successful mappings that occur. > > In either case we would still have the option of... > > %evalCorr(myFirstDS:mySecondDS); // don't care what it returns, we just > want > the side-effects.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 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.