For constants we go with the convention of all caps, which I think is standard in other languages. Although that doesn't help the situation, the parser would still see AND as a part of an expression.

We use $ in front of exported procedure names. The fight against using $ @ # seems to be in regard to taking the code global. This makes sense for vendors. It makes sense for international shops. Maybe I'm being short-sighted in not seeing our code going global? Thing is, I find our naming of procedures to be incredibly helpful. I suppose we could instead have them all prefixed as E_ and it would be equally helpful.

Every shop I've been at has used #, though I do prefer "Number" written out personally.

Kurt Anderson
Sr. Programmer/Analyst - Application Development, Service Delivery Platform

-----Original Message-----
From: WDSCI-L [mailto:wdsci-l-bounces@xxxxxxxxxxxx] On Behalf Of Charles Wilt
Sent: Monday, June 02, 2014 10:32 AM
To: Rational Developer for IBM i / Websphere Development Studio Client for System i & iSeries
Subject: Re: [WDSCI-L] Another Outline Oddity?

Though having a shop standard where variant characters ares used in variable names is a bad idea....

http://www.mcpressonline.com/rpg/the-midrange-manager-more-about-field-names.html

I'll have to see if I can find my copy of Cozzi's "blue ribbion campaign against $ @ #


Charles


On Mon, Jun 2, 2014 at 8:26 AM, Briggs, Trevor (TBriggs2) < TBriggs2@xxxxxxxxxxx> wrote:

Of course, having a shop standard where string variables and constants
always start with '$' helps clarify the code and avoids the
possibility of a reserved word conflict.

Trevor Briggs
Analyst/Programmer
Lincare, Inc.
(727) 431-1246
TBriggs2@xxxxxxxxxxx

-----Original Message-----
From: WDSCI-L [mailto:wdsci-l-bounces@xxxxxxxxxxxx] On Behalf Of
Vernon Hamberg
Sent: Sunday, June 01, 2014 10:55 AM
To: Rational Developer for IBM i / Websphere Development Studio Client
forSystem i & iSeries
Subject: Re: [WDSCI-L] 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.


--
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 message originates from Lincare Holdings Inc. It contains
information which may be confidential or privileged and is intended
only for the individual or entity named above.
It is prohibited for anyone else to disclose, copy, distribute or use
the contents of this message.
All personal messages express views solely of the sender, which are
not to be attributed to Lincare Holdings Inc., and may not be copied
or distributed without this disclaimer.
If you received this message in error, please notify us immediately at
MailAdmin@xxxxxxxxxxx or (800) 284-2006.

**********************************************************************
**********************************************************************
****************************************************************

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

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

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

This mailing list archive is Copyright 1997-2022 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.