Re: Exported Variables (was Long Constant Names)

On Thu, 6 Jan 2005 17:38:15 -0500, Paul Morgan <pmorgan@xxxxxxxxxxxxxx> wrote:
> Barbara & Scott,
> 
> Dang.  I was using just the date string without the D prefix in my testing.
> Getting SQL syntax confused with RPG syntax.  My mistake.  I know it's a
> 'bad thing' to ask for the address of a constant variable (probably trying
> to violate the constant condition) but what about %ADDR?
> 
> Why would I want to use a LIKE on a constant variable?  The linked constant
> variable could be an array index start value.  I want to iterate through the
> remainder of the array.  Would be nice to define the interator variable LIKE
> the linked constant variable start value linked into the program.  As Scott
> mentioned, it's almost as easy to link in a constant value and a
> non-constant variable.  I just hate cluttering up my program with
> unnecessary variables.
> 
> Why should I be prevented from passing a constant variable by reference to a
> non-constant parameter?  Yes it's bad.  Give me a warning about it but don't
> stop the compile.  Not my fault the developer of that interface left off the
> const keyword.  I don't have control over the procedure definition.

yes you do.  You could write an interface to the interface.  Your
interface would accept the parameter by value.  It would then call the
incorrectly written procedure, the one with the mutable parameter that
is really a const parameter, passing the passed by value parm to the
non const parm.

-Steve