Re: CL pgm and pointer variables

[Ken Sims <mr2087@xxxxxxxxx>]

Hi Jon -

>  >> If CL character variables are aligned on a 16-byte boundary, then if you
> just receive the value from one procedure and pass it to another without
> manipulating it, you should be okay.
>
> In any language apart from CL I'd agree with you, but I've seen CL generate
> some really strange code over the years including moving input parms to a
> temp area and then back again (which would invalidate a "faked" pointer).
> Personally I don't think it is worth the risk - even if it works today .....
Are you talking about an input parameter that is a parameter coming into
the CL program (i.e. on the PGM statement) or a parameter that is being
used as input on a CALLPRC command within the CL program?  If the former, I
don't think that is applicable.  If the latter, I'd like to know how you
are able to see the code generated for an ILE CL program as I would like to
be able to look at such myself.

Ken
Opinions expressed are my own and do not necessarily represent the views of
my employer or anyone in their right mind.