Re: the need for speed

        As much as it may cause some gnashing of teeth from Jon,
        Be that as it may,   There is "Never" a reason for 

        Everywhere,  Everytime, for Everything.

        Dynamic Calls are great
        (At the appropriate time)

        Bound Calls & Service Programs are great
        (At the appropriate time)

        Procedures are great
        (At the appropriate time)

        Subroutines are Great
        (At the appropriate time)

        The job of a  "Professional"  programmer
        is to decide "What is the appropriate time"

        Taking into consideration the type of application system
        it is,   The runtime performance needed.
        The level of fore-seeable maintenance anticipated.
        (how much is it likely to change over time)
        The frequency of logical execution per run. (the performance
indicator again)

        Last but not least(here comes the spam),   
        What is the shop standard? and what  is the level of 
        the skill set who will be charged with maintaining the 
        stuff.

        Do you have your "feces consolidated"  
        when it comes to naming conventions, binding
        and rebinding methodologies, 

        Wholesale replacement of subroutines by
        Sub-procedures?   

        Nah.

        BTW,  Speed is the LAST criteria when it comes
        to deciding the above.    ALWAYS,  LAST.

        IMHO

        John Carr


        -------------------------------------------------


        From:   HwaRangRon@HwaRangRon on 11/20/99 11:05 AM
        To:     RPG400-L@RPG400-L@midrange.com@SMTP@EXCHCONNECT
        cc:      

        Subject:        the need for speed

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