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

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 ]
In a perfect world, where existing app's can be rewritten at will and the
sun shines all the time: no /copy's anywhere but D specs sounds fine to me
too.  In the real world, where we often get stuck working on stuff written
by others and to standards of long ago: the editor makes a difference.
Using Code/400 and just having to double click on the /copy member's name
and then select edit /copy or view /copy makes life a lot easier.  Those
existing /copy's are still better than the repeated copies of the same
code...

-----Original Message-----
From: James Rich [mailto:james@eaerich.com]
Sent: Thursday, March 21, 2002 2:25 PM
To: rpg400-l@midrange.com
Subject: RE: /COPY one extra thing to look at (was: Defining a function
ke y...)


On Thu, 21 Mar 2002, Westdorp, Tom wrote:

> Are you using Code/400?  Much better with /copy's, easy open for browse or
> edit.

It doesn't matter what code editor you are using, Nathan is right:  if you
are using /COPY for C specs and variables then it is far better done in a
subprocedure.

James Rich
james@eaerich.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.