Re: Odd CALLPRC behavior when using RPG indicator with RTNVAL -- RPG400-L

Subject: Re: Odd CALLPRC behavior when using RPG indicator with RTNVAL
From: Brian Johnson <brian.johnson.mn@xxxxxxxxx>
Date: Fri, 13 Mar 2009 10:48:58 -0500
List-archive: <http://archive.midrange.com/rpg400-l>
List-help: <mailto:rpg400-l-request@midrange.com?subject=help>
List-id: RPG programming on the IBM i / System i <rpg400-l.midrange.com>
List-post: <mailto:rpg400-l@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/rpg400-l>, <mailto:rpg400-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/listinfo/rpg400-l>, <mailto:rpg400-l-request@midrange.com?subject=unsubscribe>

On Fri, Mar 13, 2009 at 10:23 AM, Barbara Morris <bmorris@xxxxxxxxxx> wrote:

Join me in the green-on-black ribbon campaign against lying to the
compiler. 8<
I will not lie to the compiler.
I will not lie to the compiler.
I will not lie to the compiler.
(I'm not using cut and paste, honest)
I will not lie to the compiler.

That's what prototypes are for. If you are going to start a ribbon campaign
make it to get prototypes in CL. Prototypes are one of the best things in
RPGIV, Commands are great prototypes for program calls. When will CL
support prototyped procedure calls? I think I'll revise my best-practices
list to include "don't make unprototyped calls". That rules out CALLPRC
command... and CALL command, oh my!

As an Amazon Associate we earn from qualifying purchases.

This mailing list archive is Copyright 1997-2025 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.