Re: Granularity of Modules

Mike,

Grouping procedures in a module allows those procedures to share static
(global to the module) variables in the module.  This includes any file
definitions.  For example, any procedures that worked with the same file
would have to be in the same module.

Other than data sharing there isn't much reason that I can see to put more
than one procedure in a module or more than one module in a service program.
Grouping procedures into modules or modules into service programs might make
an application easier to manage (not as many objects) but could cause
version control problems (simultaneously changing two parts of a module or
service program).

There really is no equivalent of module or service program to Java class.
If you code the module or service program right you can get close to a Java
class - if  the class only had static members.  The module or service
program might be more like a  Java package.

Paul