× 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.



In general I would agree with you. But, when you are performing
multiple tests
and as soon as you fail the first one, it is generally acceptable to
return immediately.

On this point, we will not agree, then. But before I go: generally
acceptable by whom? By you, or by your firm, or by some standards
organization?

Some clients prefer 'Not =' to '<>'.
Not equal is only one logical test where '<>' is two logical tests.
Besides it is much easier to debug 'not =' vs '<>' when the previous
pgmr

<> and NOT = are equivalents, and fall under the "not" rule (in my opinion).

If you can write =, then why do you need <>?

If a = b ;
Something() ;
Else ;
somethingElse() ;
Endif;

Rather than:
If a <> b ;


Dennis Lovelady
http://www.linkedin.com/in/dennislovelady
--
It's great to be smart 'cuz then you know stuff.




As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.