|
On 11/16/2016 3:18 PM, Vernon Hamberg wrote:
It is well -known that we should avoid naming things the same as theI'd love to hear that talk, but the general problem is that columnar RPG
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.
'knows' a variable from an opcode because of the column the identifier
is in. Fully free RPG has to suss it out. So this abomination is
perfectly legal and compilable:
C IFLE IFEQ IFGT
C ADD 1 ELSE
C ELSE
C ADD 1 MULT
C END
but that gets weird in free:
if ifeq = then;
else += 1;
else;
end += 1;
endif;
The parser (in RDi and the compiler) gets confused. It gets better with
eval:
if ifeq = then;
eval else += 1;
else;
eval end += 1;
endif;
The parser is pretty good at what it does, but it can get lost if I do
something like put unmatched parens and quotes in weird places.
As an Amazon Associate we earn from qualifying purchases.
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.