Re: CF-Spec - another call for opinions -- RPG400-L

× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



One vote here for Option 2 - I'll live with adding the Eval/CallP in the event
that you add a conflicting op-code in the future.  I lived with this for years
in COBOL and despite the large numbers of reserved words added by later COBOL
standards, only ever had to change the name of one variable.  Adding back an
Eval (not an option in COBOL) is so trivial that I would have no problem with
it.

As long as when add an opcode there is no way that my existing code would still
compile I see no problem.

I do NOT want option 4 or anything similar.


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

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.