RE: RE: Trials and tribulations of QMHSNDPM (Was: No Subroutines...)

I don't like that idea.

At least by using multiple copy books you can tell what's in the copy book by 
where the /copy is.

In addition, I keep mine in separate source files.

QPROTOSRC, for definitions (d-specs prototypes, ds templates, constants ect.)
QCOPYSRC, for code (c-specs or entire procedures including p,d,c-specs)

Charles Wilt
--
iSeries Systems Administrator / Developer
Mitsubishi Electric Automotive America
ph: 513-573-4343
fax: 513-398-1121
 

> -----Original Message-----
> From: rpg400-l-bounces@xxxxxxxxxxxx
> [mailto:rpg400-l-bounces@xxxxxxxxxxxx]On Behalf Of Hewitt, Rory
> Sent: Thursday, July 28, 2005 12:48 PM
> To: rpg400-l@xxxxxxxxxxxx
> Subject: RE: RE: Trials and tribulations of QMHSNDPM (Was: No
> Subroutines...)
> 
> 
> Duane,
> 
> >>Use copybooks. 
> 
> Like many shops, mine is happy (relatively) with D-specs being copied
> in, but not C-specs. Something about being able to see all 
> the 'code'...
> Not my choice.
> 
> Now what would be even better would be able to include a 
> single copybook
> which could include multiple specs (at least D- and C-specs) and have
> the compiler sort them out and place them in the appropriate place. I
> have a precompiler which includes processing to do this, but even so,
> it's not ideal...
> 
> Rory
> 
> -- 
> This is the RPG programming on the AS400 / iSeries (RPG400-L) 
> mailing list
> To post a message email: RPG400-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
> or email: RPG400-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/rpg400-l.
> 
>