|
mark wrote: >>Well, there's more to software development than just >>coding. Unfortunately, I never got agreement to the >>need for XOR. After all, you can use the <> operator >>to get the same functionality. > >That works for one condition, not multiple conditions. Well, if you consider the binary operator XOR, the expression: (A) <> (B) <> (C) would have the same result for all values of A, B, and C as: (A) XOR (B) XOR (C) This expression returns *ON if all 3 operands are *ON, which is probably not what you want. I think what you're asking for is a function, XOR(c1:c2{:c3}...), which would return *ON only if exactly one of the indicator operands was *ON, and *OFF otherwise. You could easily write your own procedure to do that if it's the kind of thing you need to do often enough. Cheers! Hans Hans Boldt, ILE RPG Development, IBM Toronto Lab, boldt@ca.ibm.com +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to MIDRANGE-L@midrange.com. | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com. | To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: david@midrange.com +---
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.