RE: parameter passing pitfall

[Ken Sims <ken@xxxxxxxxx>]

Hi Buck -

> >Why doesn't the compiler check that the arguments are
> >the correct length, not just the correct type?
>
>Because of CONST.  One of the things that CONST does is to "map" somewhat
>mis-matched parameters.

This is true, which is why your statement in another message ...

>"twentychar" is not _guaranteed_ to hold anything except '12' in the first
>two columns.  The remaining 18 are undefined, and are whatever happens to
>fall after fld2 in memory.

is NOT true.

Since CONST is specified and the length of the value specified is less than
the length of the parameter, the compiler creates a work area, loads with
it the value, pads it on the right with blanks, and passes the address of
the work area.

Ken
http://www.ke9nr.org/
Opinions expressed are my own and do not necessarily represent the views of
my employer or anyone in their right mind.