RE: Suggestion: File to use when compile

keyword is nice for the example you have.  But if the thing that you want to 
override is part of the compile command parm, I think, it would be nice for ibm 
to provide a /ovrparm that is dynamic enough to override it without developer 
have to ask for a keyword and wait to 10 years <g> to get it.

-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx
[mailto:rpg400-l-bounces@xxxxxxxxxxxx]On Behalf Of Tony Carolla
Sent: Wednesday, October 13, 2004 3:51 PM
To: RPG programming on the AS400 / iSeries
Subject: Re: Suggestion: File to use when compile


It just seems to me that taking advantage of what's already included
in the language would be better to expand on.  For example, on the
ExtFile keyword, perhaps allow multiple parameters, ex.

ExtFile('lib/filename':'lib/filename')

where the second paramenter (which could never be a variable) would
point to the file to use during the compile.  Perhaps even include a
parm for the system name that contains the file.  In this way, you
aren't really adding another layer to the whole mess, with CL commands
(never mind what happens when the CL commands change -- what about
positional parameters, etc??? -- that's scary, if you ask me).

I agree that if you are going to start embedding commands in your
program for the compiler, this really is going too far.