RE: CL code formatting and programming etiquette

Well, Vern, I'm still stuck on V5R1 using WDSc 7, but maybe it'll do the
same thing. WDSc is good for keying CL - unless one prompts (which, as I
said, I do all of the time) and then it is slow. So I use SEU for CLs.

But maybe I wasn't clear enough about my formatting. For example:

DCL VAR(&NAME) LEN(1)
DCL VAR(&NAME2) LEN(2)

CHGVAR VAR(&FIELD) VALUE('Something')
CHGVAR VAR(&ANOTHERONE) VALUE(&WHATEVER *TCAT &FIELD)

Not separate lines for VAR() and LEN(), just aligned.

But your point about metrics is true. .-) But they wouldn't know a metric
here if it bit 'em in the butt.

Jerry C. Adams
IBM i Programmer/Analyst
If my fellow citizens want to go to Hell, I will help them. It's my job.
-Justice Oliver Wendell Holmes (in a private letter)
--
A&K Wholesale
Murfreesboro, TN
615-867-5070


-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Vern Hamberg
Sent: Tuesday, May 29, 2012 12:11 PM
To: Midrange Systems Technical Discussion
Subject: Re: CL code formatting and programming etiquette

In RDP one can get each parameter on a separate line - at least, START on a
separate line - this does make things easier to read, albeit more lines of
code - hey, that makes us more productive according to metrics, right??


On 5/29/2012 10:56 AM, Jerry C. Adams wrote:

-snip-

I, also, try to line up things. For example, a string the DCLs will
all have the TYPE() LEN() and VALUE() keywords in the same columns.
For me it's easier to read than zigzagging through the definitions.

-snip-
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe,
or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a
moment to review the archives at http://archive.midrange.com/midrange-l.