|
On 03/03/2006, at 3:20 PM, Mike Pantzopoulos - (H/O) wrote:
I found the problem with the &RETURN parameter in midrange and got that to work as well by extracting only the first byte. Is this some issue with the way the compiler returns a value through the procedure name that can't be mapped directly to how CL works internally?
It has nothing to do with how CL works internally. It has everything to do with really dumb design.
When ILE CL was created the only other ILE language was C. C has the rather stupid habit of widening parameters and return values. Thus whoever implemented the CL CALLPRC tried to be compatible with C and gave little or no thought to the possibility that other ILE languages might be callable from CL in some future release.
This problem also exists when calling CL procedures from RPG. RPG has a (relatively recently) provided options on the EXTPROC keyword to control this behaviour. CL should have provided the same set of options.
Regards, Simon Coulter. -------------------------------------------------------------------- FlyByNight Software AS/400 Technical Specialists http://www.flybynight.com.au/ Phone: +61 3 9419 0175 Mobile: +61 0411 091 400 /"\ Fax: +61 3 9419 0175 \ / X ASCII Ribbon campaign against HTML E-Mail / \ --------------------------------------------------------------------
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.
midrange.com
