Booth wrote:

>>The RETURN opcode in RPG Returns immediately to its caller upon being 
>>executed.  I mean "Where ever it is executed".   I personally use  a
>>subroutine I call EXIT in everyone of my programs.  It does the  RETURN
>>opcode.  Where ever I am in the program, If the user wants to leave,  I
>>EXSR EXIT.
>
>John;
>I like this idea.  I never thought of it, but then, I'd never do a return
>anywhere but at the bottom of the cycle anyway.  And if I was at the
>bottom of the cycle and LR was on, or set on, why would I add in a RETRN? 
>I will admit to writing
>     C             MOVE  *ON         *INLR
>     C  NLR       RETRN                              though.

Whether you condition the RETRN on NLR or not the code will perform
identical function.  If LR is on when the RETRN is executed, the program
goes away.  If LR is not on when the RETRN is executed, the program does not
go away.  In both cases, the program will return to the caller.
>
>I think perhaps I need a standard sub-routine for *INLR time, to FREE all
>progams called.  I don't like 500-line plus programs, so I tend to write
>scads of small callable programs.
>
>damn, sometimes I learn things I didn't want to know.  
>
>Thanks to both John and Charlie.
>


Charlie Massoglia, Massoglia Technical Consulting, Inc.
PO Box 1065, Okemos, MI 48854, USA
517-676-9700  Fax: 517-676-1006  EMAIL: cmassoglia@voyager.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 MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---


This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2019 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available here. If you have questions about this, please contact [javascript protected email address].