× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.




Hi Ken,

The syntax checker should be looking at the beginning and ending of the
statement, so it looks like a bug to me. Would you mind opening a PMR for
this?

Thanks,
Taryn Morris
Developer - IBM RDi developer


|------------>
| From: |
|------------>
>--------------------------------------------------------------------------------------------------------------------------------------------------|
|Ken Killian <kkillian@xxxxxxxxxxxx> |
>--------------------------------------------------------------------------------------------------------------------------------------------------|
|------------>
| To: |
|------------>
>--------------------------------------------------------------------------------------------------------------------------------------------------|
|"WDSCI-L@xxxxxxxxxxxx" <WDSCI-L@xxxxxxxxxxxx> |
>--------------------------------------------------------------------------------------------------------------------------------------------------|
|------------>
| Date: |
|------------>
>--------------------------------------------------------------------------------------------------------------------------------------------------|
|08/21/2014 10:12 AM |
>--------------------------------------------------------------------------------------------------------------------------------------------------|
|------------>
| Subject: |
|------------>
>--------------------------------------------------------------------------------------------------------------------------------------------------|
|[WDSCI-L] RDi 9.0 LPEX syntax checking on Constants... |
>--------------------------------------------------------------------------------------------------------------------------------------------------|
|------------>
| Sent by: |
|------------>
>--------------------------------------------------------------------------------------------------------------------------------------------------|
|"WDSCI-L" <wdsci-l-bounces@xxxxxxxxxxxx> |
>--------------------------------------------------------------------------------------------------------------------------------------------------|





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.



As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.