Re: the need for speed

["David Morris" <dmorris@xxxxxxxxxxxxx>]

Ron,

If the routine you are calling is used in multiple programs, I would make it a 
sub-procedure.  If the routine is only used in a single program and would 
benefit from a well defined interface, I would make it a sub-procedure.   In 
most 
cases I use  sub-routines to break code up into more manageable chunks.  I 
wouldn't worry about speed of calls at all (that doesn't mean I would create 
a sub-procedure to increment an index.)

David Morris


>>> HwaRangRon@aol.com 11/20/99 09:05AM >>>
I came away from one of Jon's sessions at Common with the distinct impression 
that every subroutine should be changed to a sub-procedure. I think I heard 
him say that, but I probably misunderstood (as usual) what he was saying.

I was reading the manual this morning and came across this:

QUOTE:
Each character in the string is converted to a two-byte hexadecimal 
equivalent using the subroutine GetHex. 
Note that GetHex is coded as a subroutine rather than a subprocedure, in 
order to improve run-time performance. An EXSR operation runs much faster 
than a bound call, and in this example, GetHex is called many times.
:ENDQUOTE 

Anybody care to comment. Procedures over subroutines. Mix and match like 
everything else? Best tool for the job, or follow the procedures?

Ron

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