Re: the need for speed

Jon,

The best way I can describe this is with some examples.  The simplest is when 
testing to see if constant parameters which are omissible/non-passable have 
been passed.  It would be nice to create a procedure that returns a 
passed/not-passed 
flag.  As you know you cannot simply test for a null pointer.  For this reason 
I usually 
put this in a subroutine.  If Ceetsta allowed a level (like receive message) 
then I could 
encapsulate this in a separate routine.  if passed(parm1)... etc.  I guess I am 
just lazy.

Another case would be to register an exit for a caller.   I have created many 
routines 
that build temporary areas and return a handle that is used to retrieve 
information from 
those temporary areas.  It would be nice to be able to register an exit -for- 
the caller so 
that I can avoid final call (which is easy to forget) processing in every 
routine which use 
these routines.

David Morris


>>> Jon.Paris@halinfo.it 11/22/99 04:10PM >>>


 >> I can think of one case where you are forced to use a subroutine or inline
code that would be best placed in a sub-procedure.

Can you explain a bit more David please - I don't understand what you're saying
here - I've used CEE APIs in subrpocedures and directly. Where is the problem ?


+---
| 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
+---