Re: Passing a Char to a Varchar in RPGLE Procedure Interface

I apologize about my response yesterday. I was so excited that it worked with RPGLE I completely forgot to test with CL before replying.
The naysayers seem to be correct. The conversion to Varchar does not occur with CL.
I declared a CL variable and populated it with a string of about 20 characters and invoked the sub-procedure twice, once with the CL parameter declared as *BYREF and the other as *BYVAL and then used debug to view the contents of the passed parameter once the procedure was entered..

The *BYREF test displayed garbage. I couldn't see the value placed into the originating CL variable. .

The *BYVAL test displayed the value, but with the first two bytes missing, presumably because the procedure was expecting a Varchar, and it ignored the first two bytes for EVAL display purposes.

I'd prefer to not have to create separate procedures. The procedure in fact is already a wrapper with some logic that invokes another procedure which also requires a varchar. I can get over this by moving the Char parameter in the first procedure to a Varchar and then using the varchar as the parameter to the second procedure. It's not elegant, but enables a single procedure to be used for the function regardless of the source language.

It's a great shame that the various compilers aren't in synch.





_______________________________________________________________________________________

The information transmitted in this message and its attachments (if any) is intended
only for the person or entity to which it is addressed.
The message may contain confidential and/or privileged material. Any review,
retransmission, dissemination or other use of, or taking of any action in reliance
upon this information, by persons or entities other than the intended recipient is
prohibited.

If you have received this in error, please contact the sender and delete this e-mail
and associated material from any computer.

The intended recipient of this e-mail may only use, reproduce, disclose or distribute
the information contained in this e-mail and any attached files, with the permission
of the sender.

This message has been scanned for viruses.
_______________________________________________________________________________________