× 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.



It appears to me that you are worried about passing more data than
necessary.  Remember that RPG passes parms by reference (by default) so if
you are passing the parm you are in essence just passing the pointer to it
behind the scenes.  There is no need to define the parm as being a pointer,
by default that is what is being passed anyway.  If the field in the called
program is defined larger than what has been passed then you have to be
careful not to use more than was passed (the length parm can be used here).

Scott Mildenberger

> -----Original Message-----
> From: Smith, Nelson [mailto:NSmith@lincare.com]
> Sent: Wednesday, February 20, 2002 7:20 AM
> To: 'rpg400-l@midrange.com'
> Subject: RE: Trigger parameter prototypes
>
>
> Thanks Tom, that does work, but I'm still confused about the
> *VarSize.  It
> appears that BfrRcd, BfrDS, BufferChr, and BufferAry would
> still all be
> 32767 characters long.  So what would be variable about it
> and is there any
> way to have the first parameter only take up the space
> designated in the
> second parameter?
>
> Now in my case, I'm passing the buffer on along to a second
> level program,
> so I suppose I could DIM the BufferAry to the value of
> BufferLength and then
> pass a pointer to that array.  At least then, the second
> level program would
> only deal with the actual size of the data buffer.  Does that
> sound right?
>


As an Amazon Associate we earn from qualifying purchases.

This thread ...


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.