Re: CL Parameters sharing memory?

That was not my statement - it was straight out of the CL programming manual. There is much more in that chapter that describes other situations.

If what you say is true, then nothing would work if you use a variable of the size of a declared parameter. I think I just don't understand what you are saying. Sorry. Too early and snow on the ground.

Vern

Tom Liotta wrote:

Vern Hamberg wrote:

"Character string constants of 32 bytes or less are /always/ passed with a length of 32 bytes (padded on the right with blanks). If a character constant is longer than 32 bytes, the entire length of the constant is passed. If the parameter is defined to contain more than 32 bytes, the CALL command must pass a constant containing exactly that number of bytes. Constants longer than 32 characters are */not/* padded to the length expected by the receiving program."

Constants, yes, including quoted constants with trailing blanks. But
not variables with trailing blanks. In effect, near as I can tell,
when the CALL command is analyzed, it's done after variable
substitution.

The variable value becomes part of the CALL command string. For
subsequent purposes, the variable is then out of the picture. The
value effectively is converted into a constant, and the length of
that constant at that point doesn't include the trailing blanks from
the variable.

Tom Liotta