RE: external subprocedures setting on LR: performance impact?

I've worked in a one page or less per subroutine shop for a long time.  The
same standard applies to procedures.  It always made sense to me.  The idea
of modular programming is to break a process down into little independent
pieces so it's easy to change or extend.  An application with hundreds of
procedures would have a several hundred page listing, but it would still
have a several hundred page listing if it had five procedures. 


Apologies for the incoherent but vaguely foreboding trailer our mail server
appends to all messages.

Joel Fritz 
> -----Original Message-----
> From: Dan [mailto:dbcerpg@xxxxxxxxx]
> Sent: Wednesday, April 09, 2003 1:07 PM
> To: RPG programming on the AS400 / iSeries
> Subject: RE: external subprocedures setting on LR: performance impact?
> 
> 
> I dunno, Buck.  If I followed the one proc/one page rule, I'd 
> have hundreds of procs for a given
> application, each having logic that wouldn't be used anywhere 
> else.  Ok, so *maybe* you're not
> limiting yourself to *absolutely* one page.  I would remind 
> you that several weeks ago, I was the
> one getting beat up by Jon & Barbara & others in this very 
> list for refusing to create one-line
> subroutines, i.e.:
>

/***************  Big Snip *****************************/
 _______________________________________________
>> 
NOTICE:
All e-mail sent to or from this e-mail address will be received or otherwise
recorded 
by The Sharper Image corporate e-mail system and is subject to archival, 
monitoring, review by and/or disclosure to Sharper Image security and other 
management. This message is intended only for the use of the addressee and
may 
contain information that is privileged and confidential. The contents of
this message 
may contain personal views which are not the views of The Sharper Image. If
you are 
not the intended recipient, dissemination of this communication is
prohibited.