Re: Additional RPGLE Enhancement Requests

>In a message dated 97-07-17 22:07:07 EDT, mcalabro@commsoft.net (Buck
>Calabro) writes:
>
>> Why not use ENDSR to prematurely leave a subroutine?
>
>Because there can only be one ENDSR per subroutine and it has to be the last
>statement.  However, you can put a tag as factor one of the ENDSR and GOTO
>that tag.  Thus:
>
>       C           VLDDAT    BEGSR                
>       C*                                         
>       C           DATE      IFGT EXPDAT          
>       C                     MOVE 'E'       RTNCOD
>       C           GOTO     SREND                
>       C                     ENDIF                
>       C           SREND          ENDSR                
>
>I only suggest this for those of you who said they might not mind something
>like:
>
>       C           GOTO         *SREND                
>
>because what you can do now is not so different..

The point of this discussion was to suggest possible ways to use structured
code; to avoid the GOTO.  I understand that the *current* language definition
requires me to have matched BEGSR ENDSR pairs.  I'm suggesting a change
to that specification.

Other folks in the discussion were suggesting a new opcode to "leave a 
subroutine early."   I just thought that we already have a "leave 
subroutine" (ENDSR) opcode; why not simply reuse it for the case when 
we want to leave early?

Buck Calabro
Commsoft, Rennselaer, NY
mcalabro@commsoft.net

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* This is the Midrange System Mailing List!  To submit a new message,   *
* send your mail to "MIDRANGE-L@midrange.com".  To unsubscribe from     *
* this list send email to MAJORDOMO@midrange.com and specify            *
* 'unsubscribe MIDRANGE-L' in the body of your message.  Questions      *
* should be directed to the list owner / operator: david@midrange.com   *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *