|
Ignore that last post. I had jumped into the middle of this thread, and while reading later I found the original message in another thread where Denis Robitaille said: ..... Note that we're not really making the opcode names reserved since we'd still allow "CF eval read = x", and in fact, coding EVAL would be required if the target variable name is the same as an opcode name. As a result, the problem is not as bad as the appearance of new statements in other languages, especially COBOL. But it would be something new for RPG programmers. so the issue of reserved words has already been broached. +--- | 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.