RE: Adoption of new RPG techniques

["Booth Martin" <Booth@xxxxxxxxxxxx>]

While the "rules" you have are clear to you the maintenance programmer that
comes after you will never know these rules and none of your code will keep
its current set of rules. 
 
A few extra rows is a small cost and does add clarity for normal & ordinary
RPG programmers.
 
 
---------------------------------------------------------
Booth Martin http://www.MartinVT.com
Booth@xxxxxxxxxxxx
---------------------------------------------------------
 
-------Original Message-------
 
From: RPG programming on the AS400 / iSeries
Date: Tuesday, August 05, 2003 5:13:53 PM
To: 'RPG programming on the AS400 / iSeries'
Subject: RE: Adoption of new RPG techniques
 
>would you like to try again?
Nope, I wouldn't like to try again, and I still like mine better. I have a
methodology for indenting just like you do, they are just different. I
don't like to take up 20 lines of code for a couple of statements when I
could take up 2 or 3. Here is my method:
 
1. If the line of code extends beyond 80 take everything after '=' and put
it two spaces after the beginning of the line before it.
batch.customerId =
#CtoN(DOMXPath_getAttrValue(root: 'Batch/customerId': *Omit));
 
2. If it still is too long take the parameters and chop them off and add
them to the next line two spaces after the name of the sub proc.
 
DOMParser =
DOMParser_init(
pSourceType: pSourceString: pValidate: 37: pErrorProcPtr);
 
3. If that is still too long I just start lining up the parms vertically
until it does fit.
 
DOMParser =
DOMParser_init(
pSourceType:
pSourceString: pValidate: 37: pErrorProcPtr);
 
4. I put spaces after each colon to clean up the multiple parms on one
line.
 
There you go. . .
 
 
 
Aaron Bartell