RE: CallP Versus Program 'CALL'

To CallP or not to CallP, that is the question.

My personal standards:
If I am calling an external program... I will specify CallP. This way I can scan for the "CallP" and locate every time the program makes an external call.

If I am calling an internal procedure... I will not specify CallP as I treat internal procedures like function calls.

It is definitely a personal choice (or company standards issue)

To EVAL or not to EVAL... Unless it is EVALR.... I can think of no reason at this time why one would use EVAL in /Free, but then... up until a couple years ago, I would always code A = A + B; instead of A += B; (I do not like coding that reminds me of that J word language, java -- oops I said it... need that bar of soap to wash my mouth now.)

Rich




-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx [mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of Jerry C. Adams
Sent: Sunday, February 10, 2013 2:14 PM
To: 'RPG programming on the IBM i (AS/400 and iSeries)'
Subject: RE: CallP Versus Program 'CALL'

Putting a CALLP, just to be clear, is like putting an EVAL on a free format line. My boss (a .Net programmer) in days gone by could understand a = B + C, but EVAL would have thrown him for a loop.

Sort of reminds me (now I'm showing my age) when in RPG II we could code
C ADD A B
Instead if
C B ADD A B

Which is clearer?

Jerry C. Adams
IBM i Programmer/Analyst
In a democracy the majority of the citizens is capable of exercising the most cruel oppressions upon the minority. -Edmund Burke