Re: Is Apex dead as an environment for Ada & Java?

[jim_snead <basswoodNObaSPAM@my-deja.com.invalid>]

In article <81s370$7am$1@nnrp1.deja.com>, mike_zebrowski@my-deja.com
wrote:
> Apex subsystems help prevent circular references.
> Ada95 naming coventions do not.
> Mike Zebrowski
> Sent via Deja.com http://www.deja.com/
> Before you buy.

Here is an approach to prevent circular dependencies
which is enforcable by using an Ada 95 compiler.

Say you have a package hierarchy called Kappa and one
called Delta.  Delta is allowed to "with" anything in
Kappa but the converse is not true. The Kappa source
is located in the path called /code/Kappa and the
Delta source is located in the path called /code/Delta.

The enforcement procedure using the Ada compiler
is to allow the Delta developers the path:
  ADA_INCLUDE_PATH /code/Delta:/code/Kappa

The Kappa developers are allowed this path:
  ADA_INCLUDE_PATH /code/Kappa

Note that the Kappa team can try all they want
to "with" Delta code. They won't succeed unless
the software lead grants them the Delta path.

This approach is simple and enforceable. I don't
like the fact that Apex has features as complicated
as subsystems to accomplish this simple effect.
The tool effectively locks you into a specific approach
and you become a captive Apex customer because
of some outrageous marketing features.


In any event, there are many valid reasons to have
circular dependencies. See Java for lots of examples.



* Sent from RemarQ http://www.remarq.com The Internet's Discussion Network *
The fastest and easiest way to search and participate in Usenet - Free!