Re: Another Outline Oddity?

Hi Edmund

If you can fix this kind of thing, that's cool. We have already been advised since forever NOT to use SQL at the beginning of variable names, and not to use reserved words for variables.

Still, this seems like a good thing to be changed.

Thanks
Vern

On 6/1/2014 8:55 AM, Edmund Reinhardt wrote:

Thanks Chuck
I didn't catch that this was pure RPG.
I tested it and I see the problem you are referring to.
This is worth a PMR as our lexer is confused. It is parsing an expression
and sees an And and assumes that it is an operation, not an operand. RPG's
lack of reserved words make life more difficult for the tooling :-)
Thanks for catching and isolating it.



Regards,

Edmund (E.H.) Reinhardt
Technical Architect for Rational Developer for i
Phone: 1-905-413-3125 | Home: 1-905-854-6195 IBM
E-mail: edmund.reinhardt@xxxxxxxxxx
RDi YouTube: 8200 Warden Ave
www.youtube.com/user/IBMRational#g/c/62DF24D5BCD43501 Markham, ON L6G 1C7
Find me on: LinkedIn: Canada
http://ca.linkedin.com/in/edmundreinhardt/





From: CRPence <CRPbottle@xxxxxxxxx>
To: wdsci-l@xxxxxxxxxxxx,
Date: 31/05/2014 05:05 PM
Subject: Re: [WDSCI-L] Another Outline Oddity?
Sent by: "WDSCI-L" <wdsci-l-bounces@xxxxxxxxxxxx>



On 30-May-2014 16:49 -0500, Edmund Reinhardt wrote:

On 30-May-2014 10:35 -0500, Gerald Kern wrote:

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.

<<SNIP>> the dynamic outline parser is independent of the program
verifier and compiler and does not have deep SQL understanding so it
is getting confused with SQL reserved words as it tries to find the
end of the SQL statement, so it can get back to RPG parsing.

I've inserted the OP just above that most recent reply. I am
confused about the most recent reply, because the code shown is purely
RPG, no SQL at all. That is, the pure RPG assignment shown is little
different than the RPG string EVAL\assignment expression: X=Y+Z;

So, there would be no SQL parsing taking place, from which the
compiler code can "get back to RPG parsing"; i.e. the compiler parsing
for that code-sample will begin and end as RPG parsing.?

--
Regards, Chuck
--
This is the Rational Developer for IBM i / Websphere Development Studio
Client for System i & iSeries (WDSCI-L) mailing list
To post a message email: WDSCI-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/wdsci-l
or email: WDSCI-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/wdsci-l.