RE: RFE - Enhance CL/ILE CALLPRC command to support External Programs

[Justin Taylor <JUSTIN@xxxxxxxxxxxxx>]

Not in that particular case. I mean if you're given a procedure that has the same name as an op code. 
________________________________________
From: Alan Campin [alan0307d@xxxxxxxxx]
Sent: Friday, March 16, 2018 3:06 PM
To: Midrange Systems Technical Discussion
Subject: Re: RFE - Enhance CL/ILE CALLPRC command to support External Programs

I am sorry but you lost me there. Procedure name can be anything you want
to call it.

How is GetCurrentPort going to clash with a op code?

Example.

On Fri, Mar 16, 2018 at 12:55 PM, Justin Taylor <JUSTIN@xxxxxxxxxxxxx>
wrote:

> Unless the procedure name conflicts with an op code, then you need CALLP.
>
>
>
> -----Original Message-----
> From: Alan Campin [mailto:alan0307d@xxxxxxxxx]
> Sent: Friday, March 16, 2018 2:50 PM
> To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
> Subject: Re: RFE - Enhance CL/ILE CALLPRC command to support External
> Programs
>
> Sorry, why do CALLP when I can simply do.
>
> dcl-pr GetCount ExtProc('CLPROC');
>    PR_Field1 Char(9)
> end-pr
>
> GetCount(Field1);
>
> why do I need CALLP?
>
> dcl-pr GetCount Int(10) ExtProc('Cpro');
>   PR_Field1 Char(10);
> end-pr;
>
> How do I call this using a CALLP? I can't without discarding the return
> value.
>
> If I can prototype any call, then I don't need CALLP.
>
>
>
>
> --
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
> To post a message email: MIDRANGE-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: https://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at https://archive.midrange.com/midrange-l.
>
> Please contact support@xxxxxxxxxxxx for any subscription related
> questions.
>
> Help support midrange.com by shopping at amazon.com with our affiliate
> link: http://amzn.to/2dEadiD