Re: Another Outline Oddity?

Just a WAG but SELECT is an opcode & it's likely that the outline parser
is getting confused as to the usage of SELECT as a variable rather than an
opcode. Which is just one of the many reasons that I do not use reserved
words or opcode as variable names.


Thanks,
Tommy Holden



From: Gerald Kern <jp2558@xxxxxxxxx>
To: WDSCi <wdsci-l@xxxxxxxxxxxx>
Date: 05/30/2014 10:37 AM
Subject: [WDSCI-L] Another Outline Oddity?
Sent by: "WDSCI-L" <wdsci-l-bounces@xxxxxxxxxxxx>



I have a project that consists of four RPGLE and three SQLRPGLE source
members.

The outline is available for all but one source member which is a free
form
SQLRPGLE (V7R1 btw)
that is showing 'unexpected token(s) ignored' tags which I think is
disabling the outline altogether. It's occurring in two places in the code
and both are where an SQL string is being composed similar to the one
shown
below.

String_SQL = Select + Where +
Q_TXRSTAT + QUOTE + Active + QUOTE +
And + Q_TXACODE + QUOTE + p_TXACODE +
QUOTE + And + Q_TXCHGDT + Today;

Not a show stopper as the program verifier shows no errors and it
compiles.
Just odd that the outline for this one program is not available.