RE: Sub procedure end specification -- RPG400-L

Subject: RE: Sub procedure end specification
From: David FOXWELL <David.FOXWELL@xxxxxxxxx>
Date: Thu, 28 May 2009 15:12:00 +0200
List-archive: <http://archive.midrange.com/rpg400-l>
List-help: <mailto:rpg400-l-request@midrange.com?subject=help>
List-id: RPG programming on the IBM i / System i <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>

-----Message d'origine-----
De : rpg400-l-bounces@xxxxxxxxxxxx
[mailto:rpg400-l-bounces@xxxxxxxxxxxx] De la part de rob@xxxxxxxxx

What, you don't prefix every 'P' spec that starts a
subprocedure with a few blank lines and /EJECT? Like this?

/EJECT
P MySubprocedure B
D MySubprocedure PI

No, more like this :

/EJECT
* List of subprocedures :
* MySubprocedure : Does some stuff
* MyOtherSubprocedure : Does other stuff

* MySubprocedure : Procedure used to do some stuff.
P MySubprocedure B

* Interface for the procedure MySubProcedure.
D MySubprocedure PI

* MySubprocedure2 : This procedure is not listed in the list of subprocedures
* because the programmer forgot, didn't realise or couldn't be bothered.
P MySubprocedure2 B

* Interface for the procedure MySubProcedure2.
D MySubprocedure2 PI

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

Re: Sub procedure end specification , Simon Coulter

This mailing list archive is Copyright 1997-2025 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.