Re: Passing *varsize parameter to another procedure

VARYING is not at all related to by reference. So I don't think I understand this issue. Yes, when called from programs that don't know about varying, they would have to insert the 2-character length - so bite the bullet and pass the extra parameter - it's simple, albeit perhaps tedious.

Lim Hock-Chai wrote:

Thanks Adam, This particular *varsize field needs to be passed by
reference. Changing it to varying field would create unnecessary work
for caller.



"Adam Glauser" <adamglauser@xxxxxxxxxxxx> wrote in message
news:<mailman.1511.1225468208.13295.rpg400-l@xxxxxxxxxxxx>...

Lim Hock-Chai wrote:

Can somebody suggest the best way to pass a *varsize parameter to a
*varsize parameter of another procedure with losing the original

length

of the variable?

If it is a character variable, consider using a VARYING character instead. That way the length is always available to whichever

procedure

needs it.

Note that this can cause a bit of pain for calling from languages that

don't fully support VARYING character as a type (CL for instance), but

it's not that hard to create utility procedure to build VARYING character strings from other string formats.