Re: Tool to convert Subroutine to SubProcedure -- RPG400-L

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

Subject: Re: Tool to convert Subroutine to SubProcedure
From: David Gibbs <david@xxxxxxxxxxxx>
Date: Thu, 20 Apr 2006 13:22:06 -0500
List-archive: <http://archive.midrange.com/rpg400-l>
List-help: <mailto:rpg400-l-request@midrange.com?subject=help>
List-id: RPG programming on the AS400 / iSeries <rpg400-l.midrange.com>
List-post: <mailto:rpg400-l@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/rpg400-l>, <mailto:rpg400-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/listinfo/rpg400-l>, <mailto:rpg400-l-request@midrange.com?subject=unsubscribe>

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.

Follow-Ups:

Re: Tool to convert Subroutine to SubProcedure , Michael_Schutte

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.