RE: FW: IBM's RPG Strategy (was: Long Procedure Names)

Since RPG doesn't allow defaults to be assigned to a parm.  I'll often code 
parms as *OMIT:*NOPASS.

This way, I make is as easy to use as possible, yet it's as powerful as you 
need it to be.

Charles Wilt
iSeries Systems Administrator / Developer
Mitsubishi Electric Automotive America
ph: 513-573-4343
fax: 513-398-1121
 

> -----Original Message-----
> From: rpg400-l-bounces@xxxxxxxxxxxx
> [mailto:rpg400-l-bounces@xxxxxxxxxxxx]On Behalf Of Tony Carolla
> Sent: Thursday, March 24, 2005 3:03 PM
> To: RPG programming on the AS400 / iSeries
> Subject: Re: FW: IBM's RPG Strategy (was: Long Procedure Names)
> 
> 
> <snip>
> > I've found that the less parms a procedure accept the less 
> frustration the programmer get when trying to use it.  Yes, 
> parms helps readability, but too many of them might not good 
> for programmer's health.
> > 
> > modularity = readability. (70% agreed).
> </snip>
> 
> I thought this way at first, but just because a proc accepts less
> parms, doesn't mean it can't be frustrating.  What about passing
> simply one parm -- a pointer to a DS?  or even a DS Array?!?!
> 
> I agree that less is better, but only if using less parms is a product
> of design, and not just getting tricky.
> 
> 
> -- 
> "Enter any 11-digit prime number to continue..."
> -- 
> This is the RPG programming on the AS400 / iSeries (RPG400-L) 
> mailing list
> To post a message email: RPG400-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
> or email: RPG400-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/rpg400-l.
> 
>