RE: CALLB vs.CALLP

[Jon.Paris@xxxxxxxxxx]

 >> That's one reason why I don't like examples that always use EXTPROC because
....

Brad I'm not sure quite what you mean and have to believe there is some
confusion here in the terminology you are using.  I say this because your own
example uses Extproc.  It is not typed in, but the compiler assumes it
nonetheless.

This code:

 D #QCmdExc        PR
 D   PR_Cmd                    1024    VALUE


Is identical to this:



 D #QCmdExc        PR                  ExtProc('#QCMDEXC')
 D   PR_Cmd                    1024    VALUE



If what you meant is "don't just point people at C routines that will do the job
for you" - then I have to disagree with that.  Using the C "system" function
(which I use almost exclusively now instead of QCMDEXC) has added value in that
it returns error information that is not simply available with QCMDEXC.



I agree that it is vital that people learn how to write their own subprocedures,
that's why we devoted a lot of space to it in the Redbook.  But there's no point
in teaching this by having folks reinvent the wheel.


+---
| This is the RPG/400 Mailing List!
| To submit a new message, send your mail to RPG400-L@midrange.com.
| To subscribe to this list send email to RPG400-L-SUB@midrange.com.
| To unsubscribe from this list send email to RPG400-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---