Granularity of Modules.

I have been having a major problem with the granularity (ie. size) of
modules. Please consider the following:

*       Several sources I have read imply that a module should consist
of a single sub-procedure.
*       Creating a program or service program then binds (by
copy/reference) so that a program could conceivably simply consist of
source code which provides the framework for invoking numerous snippets
of code via the individual sub-procedures.
*       As an old FORTRAN programmer, I'm happy with the concept of
linking like this. In essence, writing very small single focus functions
and then linking them through a binding step.
*       There is nothing to stop a module from containing numerous
sub-procedures, both local to the module and EXPORTed.
*       I can live with the idea of more than one sub-procedure in a
module as long as they are only used locally, but I'm having trouble
with the idea of modules with more than one sub-procedure. The compiler
allows this to occur and to my mind it must be very difficult tracking
the relationship between programs, modules, and sub-procedures.
*       My other beef with the module/sub-procedure relationship is the
size of the name - if the sub-procedure name can be 15 and the source
member name is 10, then we immediately have an issue. I am then faced
with having to have a naming standard which encodes the sub-procedure
name, or have to restrict my sub-procedure names to 10 characters. 

Do other ILE developers restrict themselves to a single sub-procedure in
their modules? 

Mike Pantzopoulos

EIG-Ansvar Limited
Tel  : 61 (3) 9614 3535
Fax: 61 (3) 9614 2740


*********************************************************************************************************
This email and any files transmitted with it are confidential and intended 
solely for the use of the individual or entity to whom they are addressed. If 
you are not the intended recipient, any use, disclosure or copying of this 
message is unauthorised. If you have received this message in error, please 
reply using the sender's email address. 

This footnote confirms that this email message has been scanned for computer 
viruses. EIG-Ansvar Limited does not accept liability for any loss or damage, 
whether caused by our own negligence or not, that results from a computer virus 
or defect in the transmission of this email or any attached file. 

EIG-Ansvar Limited - Australia (A.B.N. 21 007 216 506)
Email : insure@xxxxxxxxxxxxxxxx

Eig-Ansvar Limited - New Zealand
Email : insure@xxxxxxxxxxxxxxxx

*********************************************************************************************************