Re: Using prototypes...

To me, prototypes (and other include files) are source and should
therefore be in the source library--in a file with a sensible name
such as RPGLEINC.

I agree with this statement and since our production libraries
(modified_objects and base_objects) do not not normally contain source (we
have a modified_source library) I feel that the prototypes file should be in
the modified_source library and this added to the library list at compile
time (interactive or batch).

Now to convince the powers that be.

Thanks all for your input.

Rob

On Fri, May 7, 2010 at 9:36 AM, Simon Coulter <shc@xxxxxxxxxxxxxxxxx> wrote:

On 07/05/2010, at 10:21 PM, Robert Rogerson wrote:

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?

To me, prototypes (and other include files) are source and should
therefore be in the source library--in a file with a sensible name
such as RPGLEINC.

If for some reason you cannot add the source library to the compile
job description then qualify the location on the /COPY directive.

Regards,
Simon Coulter.
--------------------------------------------------------------------
FlyByNight Software OS/400, i5/OS Technical Specialists

http://www.flybynight.com.au/
Phone: +61 2 6657 8251 Mobile: +61 0411 091 400 /"\
Fax: +61 2 6657 8251 \ /
X
ASCII Ribbon campaign against HTML E-Mail / \
--------------------------------------------------------------------



--
This is the RPG programming on the IBM i / System i (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.