Kurt,
In 9.01, there was a major enhancement to provide "live" parsing (updating
the outline, content assist, hyperlink, hover info on every key-stroke).
This required writing a new RPG parser in Java. This new parser can not
handle all invalid source and will stop parsing if it hits something it
cannot understand and it will flag it with a yellow annotation on the left.
Fixing the issue will allow it to continue to do its magic.
The alternative is to go back to the static parser that uses the Program
Verifier under the covers. You can toggle between them using the
preference Remote Systems->Remote Systems LPEX Editor->IBM i Parsers->ILE
RPG - "Updated the Outline view when text is changed in the editor".
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: Kurt Anderson <Kurt.Anderson@xxxxxxxxxxxx>
To: "Rational Developer for IBM i / Websphere Development Studio
Client for System i & iSeries" <wdsci-l@xxxxxxxxxxxx>
Date: 04/09/2014 05:33 PM
Subject: Re: [WDSCI-L] Outline not working for some SQLRPGLE source
Sent by: "WDSCI-L" <wdsci-l-bounces@xxxxxxxxxxxx>
When I've had this happen it's been due to a syntactical issue in the
program. I don't recall which types of coding screw-ups cause the outline
to disappear, but some things clearly are messing up the parser.
Interesting, though, that on pre-9.01 versions I don't recall this
happening.
Kurt Anderson
Sr. Programmer/Analyst - Application Development, Service Delivery Platform
-----Original Message-----
From: WDSCI-L [mailto:wdsci-l-bounces@xxxxxxxxxxxx] On Behalf Of Bob Schuch
Sent: Thursday, September 04, 2014 3:33 PM
To: WDSCI-L@xxxxxxxxxxxx
Subject: Re: [WDSCI-L] Outline not working for some SQLRPGLE source
Jon Paris wrote:
I encountered the same problem yesterday Justin - haven't had time to dig
into it and since it turned out I had opened the wrong source ...
I have also encountered this and was told it is because the parser has
trouble parsing something in the source, usually where a reserved word is
used as a variable.
To find the error, there is a thin bar along the right side of the source
which will have a little yellow marker in it. This will indicate where the
parser fails.
I was able to remedy it on one source by changing the name of that variable
to something that was not a reserved word.
Hope this helps.
--
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.
--
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.
midrange.com
