Re: AW: CallP Versus Program 'CALL'

[Rpglist <rpglist@xxxxxxxxxxx>]

Thanks Scott I suppose I should have worded my post a little better in the beginning.  What I was trying to determine was I'd it faster to use a procedure either externally or internally defined versus coding it as a program and using the CALL 'program name'

Sent from my iPhone

On Feb 10, 2013, at 6:56 AM, Scott Klement <rpg400-l@xxxxxxxxxxxxxxxx> wrote:

> ...  the main time I use CALLP is when calling a procedure that has the 
> same name as an opcode.
>
>    callp write(fd: %addr(data): %len(data));
>
> I can't just code write() because it's the same name as the WRITE opcode.
>
> -SK
>
>
> On 2/10/2013 3:15 AM, Birgitta Hauser wrote:
> > CallP is only mandatory if you want to specify an (E) extender to trap errors.
>
> -- 
> This is the RPG programming on the IBM i (AS/400 and iSeries) (RPG400-L) mailing list
> To post a message email: RPG400-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
> or email: RPG400-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/rpg400-l.