Re: RDi 9.0 LPEX syntax checking on Constants...

It has been the behaviour forever Ken.

I don't use F5 - I just move the cursor bcd to the first line and type a space that forces it to reconsider the whole statement.

PMR is not a bad idea - this is not the only place where a failure to back off to the last (effective) end-of-statement (;) when syntax checking new/changed entries often leaves ugly messages around.


On 2014-08-21, at 10:12 AM, Ken Killian <kkillian@xxxxxxxxxxxx> wrote:

Hi,

Since I have been using LPEX over 8-years, I am considered the "Expert". So I get a lot of questions like I wrote RDI... <LOL>
<Side-Bar>

So the Developer is still using FIXED format D-Specs, and types in this:

d mylongconst c 'This is long constant that +
RNF0267E Character literal has missing trailing apostrophe; trailing apostrophe assumed.


************************
Then the developer keys in the second line, and he expects the above syntax error to disappear. <shock>
d spans two lines'

The Developer has stated to me that the LPEX Error should automatically go away, once the statement is completed.

I told the developer, this is probably because it only syntax-checks one line at time, and just do Ctrl+F5 to remove the now invalid syntax error. Then continue on...

I asked the developer, if I should open a PMR for this issue. Just thought I would ask about this before
a PMR with IBM.


-Ken Killian-


--
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.

Jon Paris

www.partner400.com
www.SystemiDeveloper.com