For the record, testing for "not equals" is not a double negative.
That would be something like "not not equals" (does that even compile?)
The phrase double negative implies redundancy, which David's "if"
statement doesn't have.
You are correct. I meant to use "IF FIELD <> 'N'", or "IF myIndic <> *Off"
which the mind does turn into a double negative whether we like it or not.
How much clearer and simpler to say "If myIndic = *ON" or simply "IF
myIndic" !
I guess in retrospect my objection is to the negative test in general (If
something is not equal to something). It stops me and makes me re-analyze
the statement (or not, which is more dangerous). The simpler, to me, is the
better and least likely to be compromised. The negative should always be
spelled e-l-s-e, in my opinion. Your mileage is free to vary.
Dennis Lovelady
http://www.linkedin.com/in/dennislovelady
--
"Half our life is spent trying to find something to do with the time we have
rushed through life trying to save."
-- Will Rogers
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.