TEAM-ADA Archives

Team Ada: Ada Programming Language Advocacy


Options: Use Classic View

Use Monospaced Font
Show Text 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: Mon, 8 Feb 1999 09:16:49 -0600
Reply-To: Samuel Mize <[log in to unmask]>
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
In-Reply-To: <[log in to unmask]> from "W. Wesley Groleau x4923" at Feb 8, 99 08:37:48 am
Content-Type: text/plain; charset=US-ASCII
From: Samuel Mize <[log in to unmask]>
Parts/Attachments: text/plain (28 lines)
W. Wesley Groleau x4923 wrote:
> > - if the type is indefinite, you can't declare an object of that
> >   type.  Of course, the full declaration makes it definite inside
> >   the private parts of the package.  But you can't have an object
> >   of that type outside the package.  This may be a problem or a
> >   feature, depending on exactly what you're trying to do.
> You may want it in the private part to make it common to all child units.
> But you could just as easily put it in a private child and have the other
> child units with it.  But if you can't have an object of that type outside
> the package, is there any point in having the type visible?

Several later messages point out that you can declare one with an

Aside from that, having it visible allows you to use it as a
parameter.  So a user program could get an item of this type
from a producer, modify it with procedures or extract data from
it with functions.

Sam Mize

Samuel Mize -- [log in to unmask] (home email) -- Team Ada
Fight Spam: see \\\ Smert Spamonam