RE: Using prototypes...

I, too, copy the prototypes into the program. But, since the new prototypes need to be written before the program, part of my procedure is to copy them into a production library that is in the library list. I do have the luxury of having a development machine so this may not be allowed for people that do development on a production machine.

Even though I am a one-man (IBM i-wise) shop, I've never seen any benefit to batch compiles. When I was part of a 6-man shop, we all compiled interactively. It only takes a few seconds even for a large program. In that environment I can ADDLIBLE at the command line or WDSc.

Another technique I use occasionally is to write a Compile procedure (CL). One can submit that, if that is the rule where you work, and ADDLIBLE there.

Jerry C. Adams
IBM System i Programmer/Analyst
--
B&W Wholesale
office: 615-995-7024
email: jerry@xxxxxxxxxxxxxxx

A verbal contract isn't worth the paper is's written on. - Samuel Goldwyn


-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx [mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of Robert Rogerson
Sent: Friday, May 07, 2010 7:21 AM
To: RPG programming on the IBM i / System i
Subject: Using prototypes...

In the shop I'm currently at Prototypes are are copied into programs at
compile time.

The programs are compiled in batch so the library list is defined in the
COMPILES JOBD. This library list does not contain the source library.
Basically the library list is:
modified_files
modified_objects
base_files
base_objects

So the prototypes file (which contains the members for the /copy) is in the
modified_objects library.

My question is, is this normal practice or shouldn't the prototypes file be
in the modified_source library and the library list in the COMPILES JOBD be
changed to add modified_source as the last library list entry?

Thanks,

Rob