RE: CF-Spec - another call for opinions

 >> I beg to differ. Having to change source on an upgrade is a very big deal.
Thats the sort of thing that prevents people from upgrading!

But the point is that it wouldn't happen in practice. How many variable names do
you think you have that might finish up as an opcode ?? 1? 2?  Consider also
that a large percentage of new functions will probably be added as built-ins.
Think about it - how many new opcodes have been added since V3R1 (4 I think) how
many new built-ins (20+?). Would any of them have clashed with a variable name?
I don't think so.

Also you wouldn't have to change on an upgrade - only when you recompiled a
program - and even then you could compile to *PRV.

I think it is one of those situations that sound as if it will be a problem, but
I suspect that if 1 out of 10,000 users experience any problems I would be
really surprised.


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