× 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.



On 11/16/2016 3:18 PM, Vernon Hamberg wrote:
It is well -known that we should avoid naming things the same as the
keywords in RPG.

Now the parsing process has been changed in recent versions of the
editor, because of the fully-free capabilities now. I believe I heard
Barbara speak about this at COMMON or at one of the CAAC meetingsI
attend. Something like the first word on a line has to be limited to a
special set - Barbara maybe will chime in on this.


Hi Vern, it was always the case that if the first word in a free-form calculation statement (statement, not line) was the same as an opcode supported in free-form, the compiler (and other tooling) assumed it was that opcode.

For various reasons, that rule also applies to free-form definitions, so if you want to define a free-form subfield or parameter with the name "SELECT" or "IF", then you have to specify the DCL-SUBF or DCL-PARM opcode, just like you would have to actually specify the EVAL opcode to assign to the name in calcs.


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.