Re: CL calling RPG Procedure returning 1byte value

[Scott Klement <rpg400-l@xxxxxxxxxxxxxxxx>]

Kurt,

The way procedures are called changed in IBM i 6.1.  So maybe you 
learned your lesson before 6.1, and it changed when you upgraded?

Of course, it also might change again in another future release.

The only way to be safe is to "follow the rules", which means to use 
EXTPROC(*CL).  If you use that, your code should work on any release 
past or present.

Using some sort of other workaround that might work today, might not 
work in a future release, etc.

-SK


On 12/4/2015 3:44 PM, Kurt Anderson wrote:
> To my knowledge, it has always been that for a RPG procedure that returns a single byte value, EXTPROC(*CL) must be specified on the prototype.
>
> However, I have recently discovered numerous scenarios that are all working perfectly where it doesn't specify EXTPROC(*CL).  I emailed the list about this back in 2011 where I found a scenario where it was working and the consensus was that we were lucky it was working.   But now I'm questioning that.
>
> Is EXTPROC(*CL) really still required for single-byte return values?  Or is the scenario that EXTPROC(*CL) is required a bit more specific than "whenever you want a CL to call a procedure that returns a 1 byte value."   I tried searching around, but didn't find an update on EXTPROC(*CL).
>
> The documentation still states that EXTPROC(*CL) is required.  Ideally I'm looking for something than "you're lucky all instances of your CLs using single-byte values returned from RPG procedures is working."  I've even started to question my understanding of what a "single byte value" is, but the documentation gives 1a as an example and that's the majority of what I'm seeing our procedures use in these cases (and one using an indicator).
>
> We're at 7.2.
>
> Kurt Anderson
> Sr. Programmer/Analyst - Application Development, Service Delivery Platform
> [cid:image002.jpg@01CD16F9.25D27630]
> web: www.customcall.com<http://www.customcall.com/> | email: kanderson@xxxxxxxxxxxx<mailto:kanderson@xxxxxxxxxxxx>
>
> A Division of Enghouse Systems Ltd.<http://www.enghouse.com/> (TSX:ESL)