Re: Outline View Quit Working

Hi Barbara - thanks for the clarification - memory gets shorter all the time!

I just make a point of never naming any variable the same as an opcode - not even BEGINNING the same as an opcode, IFIGENIA would not be something I'd use for a name. (Besides, it's misspelled!)

Vern

On 11/16/2016 3:38 PM, Barbara Morris wrote:

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.