× 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.



LOL Rory

I was inclined to say the same thing about the other guy - sheesh!! What's so hard about a different way to use FIND in the debug screen? That seems awfully old-school somehow, even on the green-screen debugger.

Vern

Rory Hewitt wrote:
Scott,

That's true, but by using the return value, he has to have the multiple
RETURNS there in his mainline code (which is the explicit point his
co-worker doesn't like). If he uses subroutines which include the RETURN
op-code, then he won't have multiple RETURN's there in his mainline code.

Like I said, I think his code is perfectly valid, and frankly, I think his
co-worker can go shove it if they don't like it... Maybe that's why I'm not
a politician.

Rory

On Mon, Mar 1, 2010 at 10:31 AM, Scott Klement <rpg400-l@xxxxxxxxxxxxxxxx>wrote:

Hello,

On 3/1/2010 11:58 AM, Rory Hewitt <rory.hewitt@xxxxxxxxx> wrote:
If you're not using local variables in the subprocedures, you are
probably
just as well off using (gasp!) subroutines, since each subroutine can
include the return statement:
Just wanted to point out that, not thing else, David was using the
return value of the subprocedure to help control the flow of his
application.

So even though he wasn't using parameters, he was still using one of the
features of subprocedures. Maybe this is just a stepping stone to
ultimately using more of the features down the road... But in any
case, he is getting the benefits of using the procedures directly in an
expression, which is enough to warrant procedures vs. subroutines.

Just an observation.


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

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.