Re: compile error on %lookup where array is the return value

[Mel Rothman <mel@xxxxxxxxxxxxxx>]

Thanks for illuminating this for me Jon.

I now see what Lim Hock-Chai was getting at: he substituted MyLookup 
for %lookup and it compiled. He wondered why %lookup didn't compile in 
a similar manner.

You pointed out that specifying CONST on MyLookup's second parameter, 
made that parameter not updatable, and therefore, made an expression 
for that parameter acceptable to the compiler.

The compiler, apparently in order to make sure that %lookup will have 
compatible data to work with at run time, only allows arrays defined 
at compile time to be used by name only.

Mel Rothman
Mel Rothman, Inc.



Jon Paris wrote:
>  >> This works because myLookup always returns 1 AND there is no %lookup
> with an expression in the array name parameter.
>
> You forced me to look again Mel - it appears to work because of the const
> keyword on the proto for MyLookup.
>
> getArray is a function that returns an array and yet is acceptable as a parm
> to MyLookup.  If you remove the const keyword it will not compile.
>
>
> Jon Paris
> Partner400
>
> www.Partner400.com
> www.RPGWorld.com