Re: Returning a pointer (was - parameters - const, value, reference)

Hi Rick, Scott,

Just to add a little to Scott's explanation of *NOPASS -- if one parameter
is prototyped with OPTIONS(*NOPASS), all the following parameters must also
have OPTIONS(*NOPASS), *and* the called procedure should be checking for
this with %parms or some similar method and acting accordingly (i.e. not
using these parms).

hth,
Peter Dow
Dow Software Services, Inc.
909 793-9050 voice
909 793-4480 fax
909 522-3214 cell


From: "Richard B Baird"
<snip>
> > Another related question. Once the called procedure has been entered,
> > where are the passed parameters stored? Are they stored in the heap? The
> > reason I ask is that I have a situation where a procedure in a service
> > program has a parameter specified as *nopass. It seems that if the
> > parameter is passed on the first call but not on the second call then
> > the second call still appears to be able to access the parameter whose
> > value remains from the first call.

From: "Scott Klement"
> Once again, that's just good luck.   Keep in mind that memory is usually
> not blanked/zeroed out when you're done with it or when you get it again.
> So, if you release memory, and allocate memory again, there's a good
> chance you'll get the same space again.