From mboxrd@z Thu Jan  1 00:00:00 1970
X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00
	autolearn=unavailable autolearn_force=no version=3.4.4
Path: 
 eternal-september.org!reader01.eternal-september.org!reader02.eternal-september.org!news.eternal-september.org!news.eternal-september.org!mx05.eternal-september.org!feeder.eternal-september.org!nuzba.szn.dk!pnx.dk!news.stupi.se!news.tele.dk!news.tele.dk!small.news.tele.dk!newsfeed-00.mathworks.com!nntp.TheWorld.com!.POSTED!not-for-mail
From: Robert A Duff <bobduff@shell01.TheWorld.com>
Newsgroups: comp.lang.ada
Subject: Re: Ada202X: Easy to use "UML private"-like components
Date: Sun, 23 Jun 2013 11:15:15 -0400
Organization: The World Public Access UNIX, Brookline, MA
Message-ID: <wcctxko270c.fsf@shell01.TheWorld.com>
References: <69246de0-4b33-4d47-b5be-a45e8c911fb0@googlegroups.com>
 <wccwqpnux8n.fsf@shell01.TheWorld.com> <b2m2csFh64iU1@mid.individual.net>
 <9qrbs8l828t3pvgves504a8fm7o1c7tcpj@4ax.com>
 <b2moeeFlshhU1@mid.individual.net>
 <91qcs81k6am9l3u3n19lj0b072lc48td69@4ax.com>
 <b2nmjsFrifnU1@mid.individual.net> <wccmwqhkm22.fsf@shell01.TheWorld.com>
 <1im71djlxwm94$.fbjv1si7kmvj$.dlg@40tude.net>
NNTP-Posting-Host: shell01.theworld.com
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Trace: pcls6.std.com 1372000516 23716 192.74.137.71 (23 Jun 2013 15:15:16
 GMT)
X-Complaints-To: abuse@TheWorld.com
NNTP-Posting-Date: Sun, 23 Jun 2013 15:15:16 +0000 (UTC)
User-Agent: Gnus/5.1008 (Gnus v5.10.8) Emacs/21.3 (irix)
Cancel-Lock: sha1:VzJumll+wdrJJSGfRYDmpnmdNx4=
Xref: news.eternal-september.org comp.lang.ada:15908
Date: 2013-06-23T11:15:15-04:00
List-Id: <comp.lang.ada>

"Dmitry A. Kazakov" <mailbox@dmitry-kazakov.de> writes:

> ... or there should be no generics.
>
> The kludge here rather is generics and inlining, both basically are macro
> expansions.

Semantics defined by macro-expansion is confusing, and should be
avoided.  I'd prefer to have generic types rather than generic
packages, and don't use macro-expansion semantics.  Eiffel shows
one way to do this.

Inlining, on the other hand, has no semantics.  Or should have none.
And it can be turned off when you want faster recompiles but slower
run time.  And inlining is inherently a macro expansion.

> To have public and private parts of the specifications makes much sense to
> me, as well as to have bodies which are not allowed for looking into (e.g.
> for shared libraries, remote objects etc).

Well, yeah, you can't very well inline across shared libraries, but I
don't see any need for that to be part of the language syntax.

- Bob