RE: o specs in sub procedure

[Joel Fritz <JFritz@xxxxxxxxxxxxxxxx>]

No, I wasn't trying to avoid global variables.  O specs can only see global
variables.  To use O specs I had the choice of using a global work variable
whose only role was to be a field in the audit report or using a subroutine
to avoid using a local variable.    

The report was before and after values for a field that was being updated
along with enough information to identify the record.  I realize there were
some other choices, but since the report was more for testing than anything
else, I didn't want to put a lot of work into it.  


> -----Original Message-----
> From: Scott Klement [mailto:klemscot@xxxxxxxxxxxx]
> Sent: Monday, March 10, 2003 11:22 PM
> To: RPG programming on the AS400 / iSeries
> Subject: RE: o specs in sub procedure
> 
> 
> 
> On Mon, 10 Mar 2003, Joel Fritz wrote:
> >
> > I think the easiest thing to do here is an externally 
> described print file.
> > Once I remembered I had Code Designer, it didn't seem so awful. <g>
> >
> 
> I must not understand your predicament.  I thought you didn't 
> want to use
> global variables -- an externally defined print file still 
> requires you to
> use global variables!
> 
> 
> > I could have used global variables and done it in a 
> subroutine.  I'm trying
> > to force myself to use subprocedures more, regardless of 
> whether they're
> > appropriate. <g>
> >
> 
> I don't understand this statement.   You can use a 
> subprocedure and do it
> exactly the same way as you would've done it with a 
> subroutine.  I don't
> understand why this is a "subprocedure" vs "subroutine" 
> topic.  Both use
> global variables and files in exactly the same way.
> 
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.