Re: Inline Syntax Checking

On May 2, 2018, at 4:41 PM, Greg Wilburn <gwilburn@xxxxxxxxxxxxxxxxxxxxxxx> wrote:

Ken,

I'm missing something. I've been writing code like that for years. What I'm saying is that if my code (or SQL statement) goes past column 80 in my source file, the syntax checker complains.

Is it something with my source PF? Or something in my RDi settings? I am on v7r3

In this example of internal procedure (function)... the syntax checker would complain on the SQL statement:
// =======================================================================
// Get Order ID from CrossDock Order column 80^
// =======================================================================
dcl-proc XdockOrdID;

dcl-pi *n char(20);
inCom char(3);
inOrd char(8);
end-pi;

dcl-s OrdID char(20);

OrdID = *blanks;

Exec Sql
Select Order_id into :OrdID from SFXDOCK Where ast_com#=:inCom and ast_ord#=:inOrd
Fetch first row only;

if SqlStt <> SqlOK;
OrdID = *blanks;
endif;

return OrdID;

end-proc;


-----Original Message-----
From: WDSCI-L [mailto:wdsci-l-bounces@xxxxxxxxxxxx] On Behalf Of Ken Killian
Sent: Wednesday, May 02, 2018 4:06 PM
To: Rational Developer for IBM i / Websphere Development Studio Client for System i & iSeries <wdsci-l@xxxxxxxxxxxx>
Subject: Re: [WDSCI-L] Inline Syntax Checking

Greg,

With **free, you can put your comments anywhere! Comments no longer start in column 81

Example:

X += 1; // increment my counter, although this is dumb comment

And you code to only limited to the length of your source file. So you can go past the punch-card limitation of 80-columns!

Which on some big SQL Statement, can be handy. Especially when I need to go past column-80!

With **Free, which has been out for over 4-years, you start in column one.

We used the help-systems RPG Toolbox for our initial learning curve:
https://www.helpsystems.com/products/rpgtoolbox-ibmi

Which has plugin for RDI! Yeah! And you can update your code and leave the source-dates alone, if you wish!
And it re-indents your code WITHOUT changing the dates. If that matters to you. We have some fossil-SEU types who love the punch-card Date columns. <LOL>

-Ken Killian-


-----Original Message-----
From: WDSCI-L <wdsci-l-bounces@xxxxxxxxxxxx> On Behalf Of Greg Wilburn
Sent: Wednesday, May 2, 2018 3:10 PM
To: Rational Developer for IBM i / Websphere Development Studio Client for System i & iSeries <wdsci-l@xxxxxxxxxxxx>
Subject: Re: [WDSCI-L] Inline Syntax Checking

I haven't used GOTO or MOVEA for 5 years. I haven't used the "/free" or "/end-free" for several years. Converted to free format H/F/D specs a while ago as well.

But I still see the column restrictions - The 7 positions on the left don't bother me as much as the 81st position on the right.

Any articles on how to get around that would be appreciated (unless it's a real PITA).

-----Original Message-----
From: WDSCI-L [mailto:wdsci-l-bounces@xxxxxxxxxxxx] On Behalf Of Ken Killian
Sent: Wednesday, May 02, 2018 3:00 PM
To: Rational Developer for IBM i / Websphere Development Studio Client for System i & iSeries <wdsci-l@xxxxxxxxxxxx>
Subject: Re: [WDSCI-L] Inline Syntax Checking

Greg,

My code starts in column-one, like my word documents, my notes, my html/xml/json and now my RPG-code.

With /Free, you have to start in Punch-Card column-8. Which is not 100%. It is only about 80% free. Because you cannot use columns 1-7, which is reserved for the old punch-card sequence numbers.

Best thing about 100% **free, you cannot code a "GOTO"/CABxx/Etc

I use "memcpy" to replace MOVEA, a punch-card restricted op-Code.

Use copy-Book for memcpy:
// ------------------------------------------------------------------------------------------
// Memory Copy (Replace MoveA in Free-Format!) :-) <Big Smile>
// ------------------------------------------------------------------------------------------

dcl-pr MemCpy ExtProc('memcpy');
Target Pointer Value;
Source Pointer Value;
Length Uns(10) Value;
end-pr;

Then use memcpy like this:

MemCpy( %addr(Body_ary):%addr(Ploc_ary):%size(Body_ary) );// movea ploc_ary body_ary


http://www.rpgiv.info/mambo/index.php?option=com_content&task=view&id=308&Itemid=9


-Ken Killian-


-----Original Message-----
From: WDSCI-L <wdsci-l-bounces@xxxxxxxxxxxx> On Behalf Of Greg Wilburn
Sent: Wednesday, May 2, 2018 2:39 PM
To: Rational Developer for IBM i / Websphere Development Studio Client for System i & iSeries <wdsci-l@xxxxxxxxxxxx>
Subject: Re: [WDSCI-L] Inline Syntax Checking

Ken,

I think I'm using that fix as well.

Not sure what you mean about the "punch card" restrictions (I'll read the link)... the only restriction I encounter is the 80-column limit.

Greg

-----Original Message-----
From: WDSCI-L [mailto:wdsci-l-bounces@xxxxxxxxxxxx] On Behalf Of Ken Killian
Sent: Wednesday, May 02, 2018 2:28 PM
To: Rational Developer for IBM i / Websphere Development Studio Client for System i & iSeries <wdsci-l@xxxxxxxxxxxx>
Subject: Re: [WDSCI-L] Inline Syntax Checking

Greg,

Interesting, I am using 100% **free ---WITHOUT-- 19th century punch-card restrictions. And I am not running in any issues.

But, I am also using the test-patch "2018-03-06 test fix".

https://whatis.techtarget.com/reference/History-of-the-punch-card

-Ken Killian-


-----Original Message-----
From: WDSCI-L <wdsci-l-bounces@xxxxxxxxxxxx> On Behalf Of Greg Wilburn
Sent: Wednesday, May 2, 2018 2:16 PM
To: Rational Developer for IBM i / Websphere Development Studio Client for System i & iSeries <wdsci-l@xxxxxxxxxxxx>
Subject: Re: [WDSCI-L] Inline Syntax Checking

So this appears to happen quite regularly after inserting an embedded SQL statement.

I can remove the error by:
1. Position to the line displaying the error 2. Remove the semicolon (again /free format) 3. Reposition cursor (down arrow) 4. Replace the semicolon.

-----Original Message-----
From: WDSCI-L [mailto:wdsci-l-bounces@xxxxxxxxxxxx] On Behalf Of Greg Wilburn
Sent: Monday, April 30, 2018 3:02 PM
To: Rational Developer for IBM i / Websphere Development Studio Client for System i & iSeries <wdsci-l@xxxxxxxxxxxx>
Subject: Re: [WDSCI-L] Inline Syntax Checking

These are the newer style annotations. CRTL-F5 won't clear them.

I can't get them to clear by typing or positioning my cursor to the line with the issue. I didn't try typing over it or wiping out the semi-colon and reinserting.

Forgot to mention this is all free format with embedded SQL.

-----Original Message-----
From: WDSCI-L [mailto:wdsci-l-bounces@xxxxxxxxxxxx] On Behalf Of Charles Wilt
Sent: Monday, April 30, 2018 2:53 PM
To: Rational Developer for IBM i / Websphere Development Studio Client for System i & iSeries <wdsci-l@xxxxxxxxxxxx>
Subject: Re: [WDSCI-L] Inline Syntax Checking

I've seen that...also on 9.6.0.1

I can usually get them to go away by going back to the line RDi thinks there's an issue with.

I don't bother to close & reopen...

Charles

On Mon, Apr 30, 2018 at 12:46 PM, Brian Parkins <goodprophet.bp@xxxxxxxxx>
wrote:

Greg, are you seeing the syntax errors as (old style) inline pink
lines, or the (new style) annotations in the margin?

If you're seeing these spurious messages as pink lines, use CTRL + F5
to clear them. If, however, you are seeing the newer style
annotations, I'm not aware of any way to clear them without
closing/opening the member as you are doing. (You can switch between
the two within the Preferences.)

Perhaps someone else has a better suggestion for clearing the annotations?

Brian.


On 30/04/2018 18:45, Greg Wilburn wrote:

I've observed the syntax checker get "out of sync" on several
occasions... It seems to happen when:

1. I insert code and reposition before finishing the insert.

2. I go back and delete the "partially completed" code that I
inserted

Sometimes the checker displays false errors on the line of code that
followed the insert. Even though the code compiles correctly, the
error is not cleared unless I close and reopen the source member.

Multiple markers at this line
- RNF3308E Keyword name is not valid; the keyword is
ignored.
- RNF0611E Parameter for keyword is missing; keyword
is ignored.


Version 9.6.0.1

Anyone else?

--
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: https://lists.midrange.com/mailman/listinfo/wdsci-l
or email: WDSCI-L-request@xxxxxxxxxxxx Before posting, please take a
moment to review the archives at https://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: https://lists.midrange.com/mailman/listinfo/wdsci-l
or email: WDSCI-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives at https://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: https://lists.midrange.com/mailman/listinfo/wdsci-l
or email: WDSCI-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives at https://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: https://lists.midrange.com/mailman/listinfo/wdsci-l
or email: WDSCI-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives at https://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: https://lists.midrange.com/mailman/listinfo/wdsci-l
or email: WDSCI-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives at https://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: https://lists.midrange.com/mailman/listinfo/wdsci-l
or email: WDSCI-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives at https://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: https://lists.midrange.com/mailman/listinfo/wdsci-l
or email: WDSCI-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives at https://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: https://lists.midrange.com/mailman/listinfo/wdsci-l
or email: WDSCI-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives at https://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: https://lists.midrange.com/mailman/listinfo/wdsci-l
or email: WDSCI-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives at https://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: https://lists.midrange.com/mailman/listinfo/wdsci-l
or email: WDSCI-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/wdsci-l.