Re: Service Programs 101

Wayne James wrote [about binding directories]:

> Since they are not *just* for service programs,
> I tend to want to create a binding directory for
> *building* my service program (listing the
> *MODULEs required) and then add the service
> program to an "application" binding
> directory where it will be *used*.

Absolutely, absolutely right.  When someone is just starting out, I
advise one binding directory (what you call an 'application' bnddir -
nice name!) because it's easier to introduce one new concept at a
time.  When they move into creating complex multi-module service
programs, I tend to advise either a 'make' program rather than
compile/bind separately -or- a separate bnddir for each complex
service program.

> There are very valid arguments for the single
> "application" binding directory, but having only
> one binding directory for everything is, IMHO,
> a *bad thing*.

While I generally agree, there is one reason for 'one bnddir for
everything:' it enforces very strict organisation.  Procedures _MUST_
be named so that there aren't any duplicates (like getName in the
customer service program and getName in the vendor service program.)
Procedures _must_ go into one module and only one module.

The downside of 'one for all' is that you can't be as flexible in your
design...

Nice addition to the thread, thanks!
  --buck