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



Yes but bear in mind when converting termination subroutines the *INLR
will NOT function as it was intended.  Each procedure/subprocedure has
it's own *INLR so if you expect *INLR in a subprocedure to unload your
program....you're wrong.... 


Thanks,
Tommy Holden


-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx
[mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of David Gibbs
Sent: Thursday, April 20, 2006 1:22 PM
To: rpg400-l@xxxxxxxxxxxx
Subject: Re: Tool to convert Subroutine to SubProcedure

Peter Dow (ML) wrote:
> There is one minor benefit to simply changing subroutines to
procedures
> -- when debugging to step through the code, you can choose to not go
> through a procedure by simply pressing F10; to step into the procedure
> you would have to press F22.

Now that you mention it ... that *IS* a fairly good reason to convert
subroutines to procedures, even if you don't do anything else.

david

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

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.