RE: /COPY one extra thing to look at (was: Defining a function key...)

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.
--
[ Picked text/plain from multipart/alternative ]
Are you using Code/400?  Much better with /copy's, easy open for browse or
edit.

-----Original Message-----
From: Nathan M. Andelin [mailto:nandelin@relational-data.com]
Sent: Thursday, March 21, 2002 12:47 PM
To: rpg400-l@midrange.com
Subject: Re: /COPY one extra thing to look at (was: Defining a function
key...)


> From: "Buck Calabro"
> There are lots of people who don't like /COPY and
> I never really understood why.  'Amount of setup'
> is much less with /COPY...

I think /copy is very useful, Buck.  But to date, I've only found it useful
for "D" specs - mostly prototypes for procedures that other programs call.
Some people use /copy members for constants and variables that are shared by
multiple programs.  That, to me may be a sign that the shared code ought to
be encapsulated into a module.  Same thing applies to "C" specs.  If you use
/copy for that, then a service program is often a better alternative.

/copy members can be a challenge if you write programs that scan and modify
source code to handle things like Y2K conversions.

Nathan M. Andelin
www.relational-data.com


_______________________________________________
This is the RPG programming on the AS400 / iSeries (RPG400-L) mailing list
To post a message email: RPG400-L@midrange.com
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/cgi-bin/listinfo/rpg400-l
or email: RPG400-L-request@midrange.com
Before posting, please take a moment to review the archives
at http://archive.midrange.com/rpg400-l.