×
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.
Then, maybe in another module,etc
IF MyFlag <> gYES;
Don't do stuff;
ELSE;
Do stuff;
Endif
Comments?
My first comment is that double negatives (if something not equal yes then..
else..) drive me up a wall. Maybe it's just me, but at a minimum the cases
should be reversed. If = no then ... else ...
But that's not your (main) point. Like you, I still see people coding that
way (using Y/N flag rather than *On/*Off conditions), and that makes me sad.
The one benefit I have seen to the approach is that you can add a new value
to the non-indicator test while with indicators you are struck with
true/false conditions. But to me that's not enough benefit. The If TRUE
... ELSE ... will always be simpler, and (if done properly) is not a matter
of subjective interpretation. What does "MYFIELD = 'X'" mean, after all?
Wouldn't customerPastDue make more sense?
Dennis Lovelady
http://www.linkedin.com/in/dennislovelady
--
"I'm not afraid to die. I just don't want to be there when it happens."
-- Woody Allen
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.