|
"Smith, Nelson" wrote: > > I'm not on V5 yet, but I do have many procedures that return an indicator > value. They are rarely (probably never, so far) called by a CL program, so > I haven't noticed a problem with them yet, but always assumed they would > work equally well with a CL as with an RPG call. Does this mean that as > soon I get to V5, that I should add *CL to my prototypes for procedures that > do return an indicator, just in case a CL needs to call them? > > I've never really quite understood how CL's relate to prototypes anyway, > since you don't define them in the CL itself. > Nelson, if you do add *CL to your prototypes, make sure you recompile all the things that use the RPG prototype - any RPG caller compiled without the *CL would stop working. Alternatively, if you do have a case where you need to have a CL caller, you could create a *CL wrapper for your procedure. Regarding how CL relates to prototypes, it doesn't really, but you can still get some of the benefits of prototypes even if all the callers or even the procedure itself isn't compiled using the prototype.
As an Amazon Associate we earn from qualifying purchases.
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.