RE: CF - One last question

>Every free format programming language I program in, 
>C, Pascal, Basic, and a lot of others, have a list of 
>"reserved words".  A reserved word is a word you 
>can not use as a function, variable, value, etc...

-snip-

>The easiest way, and in keeping in step with all 
>the other free format programming languages, 
>would be to have a set of reserved words
>for RPG.

What happens if you have a distribution application where one of the most
heavily used database fields is called CHAIN?  Renaming it is a practical
impossibility, so I guess I just couldn't use the CF-specs for this
application?  It gets worse - what if I had a database field called MONITOR.
Today, MONITOR is not a reserved word, so my CF-specs compile just fine.  

John's comments are directed toward the idea that the NEXT release may
introduce a new opcode called MONITOR, and now my program will no longer
compile because my database is using a newly reserved word.

btw, we already have reserved words in RPG IV.  Try to create a procedure
named UDATE :-)

Buck Calabro
+---
| 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
+---