TEAM-ADA Archives

Team Ada: Ada Programming Language Advocacy

TEAM-ADA@LISTSERV.ACM.ORG

Options: Use Classic View

Use Monospaced Font
Show HTML Part by Default
Condense Mail Headers

Topic: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Sender: "Team Ada: Ada Advocacy Issues (83 & 95)" <[log in to unmask]>
Date: Wed, 15 Apr 1998 09:32:16 -0500
Reply-To: Samuel Mize <[log in to unmask]>
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
In-Reply-To: <[log in to unmask]> from "Mike Brenner" at Apr 15, 98 10:09:04 am
Content-Type: text/plain; charset=US-ASCII
From: Samuel Mize <[log in to unmask]>
Parts/Attachments: text/plain (31 lines)
Mike Brenner wrote:
> The problem with renamings of packages is that they only rename
> the visible part. The biggest configuration management weakness
> is the Ada language is the lack of method of renaming a package body.
>
> By renaming the package spec and body together, as Ada permits,
> the programmer is forced to duplicate the package spec for each
> package body. This causes a lack of integrity in the copied
> package spec because a change in one might not propogate to the others,
> and worse: a change in one might not be tested against the others.

In any given compilation, you can only have one body per spec.  It
makes no sense to talk about renaming the body separately, or about
renaming the body at all: other units can't even SEE the body.

I'm not sure I have even a faint clue what you're talking about,
but my guess is that you're talking about having multiple bodies
for the same spec, e.g. to select a body based on what target
you're on.  This is done outside the language in Ada, e.g. by
selection of what file (containing a body) you will compile.

Can you give a short example of what you are talking about?

Best,
Sam Mize

--
Samuel Mize -- [log in to unmask] (home email) -- Team Ada
Multi-part MIME message: " ", " ", " " (hands waving)
Fight Spam - see http://www.cauce.org/

ATOM RSS1 RSS2