× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



<snip>
IMHO that's a good way to code a procedure.  You don't end up with all sorts of
conditioned code to get to the one RETURN at the end of the procedure.
</snip>

I agree why dig through a pile of nested if's just to find out you want to 
return???

Thanks,
Tommy Holden


-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx
[mailto:rpg400-l-bounces@xxxxxxxxxxxx]On Behalf Of Paul Morgan
Sent: Thursday, July 28, 2005 11:04 AM
To: rpg400-l@xxxxxxxxxxxx
Subject: Re: No Subroutines (was Re: Debugging many subprocedures)


Well, LEAVESR really does a branch to ENDSR so he's correct about putting
the breakpoint on ENDSR.  You're right about being able to use GOTO out of
the subroutine.  One of the benefits for using a procedure is you can only
normally exit the procedure using RETURN.

I don't understand Joe's problem with multiple RETURNs in a procedure.  IMHO
that's a good way to code a procedure.  You don't end up with all sorts of
conditioned code to get to the one RETURN at the end of the procedure.

Paul


As an Amazon Associate we earn from qualifying purchases.

This thread ...


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

This mailing list archive is Copyright 1997-2024 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 on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.