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

[rob@xxxxxxxxx]

I think that the constants and variables are a good thing in the /copy.
That way everyone uses the same field names for an INFDS, a PSDS, etc.  Now
for crud like x, y and other misc counter variables you are probably right
and that should be broken out into a service program.  And if you need
multiple INFDS, you just use the LIKEDS keyword on your other INFDS's.

Rob Berendt
--
"They that can give up essential liberty to obtain a little temporary
safety deserve neither liberty nor safety."
Benjamin Franklin



                    "Nathan M. Andelin"
                    <nandelin@relational       To:     <rpg400-l@midrange.com>
                    -data.com>                 cc:
                    Sent by:                   Fax to:
                    rpg400-l-admin@midra       Subject:     Re: /COPY one extra 
thing to look at (was: Defining a
                    nge.com                     function key...)


                    03/21/2002 03:46 PM
                    Please respond to
                    rpg400-l






> 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.