|
Jim wrote: >If you do create a bitwise AND please do not make the token 'AND' but >some other symbols, perhaps C's '&&'. It gets very confusing when AND >is both bitwise and logical. Code that looks like it should work either >doesn't or is intermittent, but it still compiles with AND as both bitwise >and logical. Especially if you allow IF statements to become true on >non *zero values. That's my biggest complaint with Basic. But of course! AND and OR should only ever refer to the logical operations. Otherwise, severe ambiguities would result. This begs the question: What syntax would you prefer for bitwise operations? a) infix operators: x ANDB y x ORB y x XORB y NOTB y (&& and || (like in C) are problematical for us since '|' is not in the invariant EBCDIC code page.) b) built-in functions: %BITAND(x:y) %BITOR(x:y) %BITXOR(x:y) %BITNOT(x) Cheers! Hans Hans Boldt, ILE RPG Development, IBM Toronto Lab, boldt@ca.ibm.com +--- | This is the RPG/400 Mailing List! | To submit a new message, send your mail to RPG400-L@midrange.com. | To subscribe to this list send email to RPG400-L-SUB@midrange.com. | To unsubscribe from this list send email to RPG400-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.