TEAM-ADA Archives

Team Ada: Ada Programming Language Advocacy

TEAM-ADA@LISTSERV.ACM.ORG

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]>
From: Tucker Taft <[log in to unmask]>
Date: Fri, 17 Jul 1998 16:23:56 -0400
Reply-To: Tucker Taft <[log in to unmask]>
Parts/Attachments: text/plain (20 lines)
> ...
> In that case, since only a single data element can be declared in
> the private part, and none at all in the public part, the use of
> "private" is really just syntactic sugar.

I'm not following.  You can declare as many data elements
as you want in the private part, as well as private
entries and subprograms.

> It's not a real private part in the sense of packages. It does
> serve as a useful delimiter for the compiler, I guess.

The "private" separates public subprograms and entries from private
subprograms and entries, and emphasizes that the
data is not accessible at all from outside the body of the type.

> Mike Feldman

-Tuck

ATOM RSS1 RSS2