× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  1.  Home
  2. RPG400-L
  3. October 2008

Re: Passing *varsize parameter to another procedure

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.

As an Amazon Associate we earn from qualifying purchases.

This thread ...
Follow-Ups:
Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.