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!news.jacob-sparre.dk!loke.jacob-sparre.dk!pnx.dk!.POSTED!not-for-mail From: "Randy Brukardt" Newsgroups: comp.lang.ada Subject: Re: Ada202X: Easy to use "UML private"-like components Date: Mon, 24 Jun 2013 15:16:30 -0500 Organization: Jacob Sparre Andersen Research & Innovation Message-ID: References: <69246de0-4b33-4d47-b5be-a45e8c911fb0@googlegroups.com> <9qrbs8l828t3pvgves504a8fm7o1c7tcpj@4ax.com> <91qcs81k6am9l3u3n19lj0b072lc48td69@4ax.com> NNTP-Posting-Host: static-69-95-181-76.mad.choiceone.net X-Trace: loke.gir.dk 1372104991 11433 69.95.181.76 (24 Jun 2013 20:16:31 GMT) X-Complaints-To: news@jacob-sparre.dk NNTP-Posting-Date: Mon, 24 Jun 2013 20:16:31 +0000 (UTC) X-Priority: 3 X-MSMail-Priority: Normal X-Newsreader: Microsoft Outlook Express 6.00.2900.5931 X-RFC2646: Format=Flowed; Original X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.6157 Xref: news.eternal-september.org comp.lang.ada:15924 Date: 2013-06-24T15:16:30-05:00 List-Id: "Robert A Duff" wrote in message news:wccppvc26ef.fsf@shell01.TheWorld.com... ... > No, that's not at all what I meant. I meant that a package would > come in three parts: > > package P is > ... > end P; > > package private P is -- Just making up syntax here. > ... > end P; > > package body P is > ... > end P; > > Normally stored in 3 separate source files. There would be no > private part syntax like we currently have. ... > My suggestion is trivial to implement. And it wouldn't be "as well", > it would be "instead of". I don't buy this. The specification would not have enough information to be usable, so compilation of it would be worthless. But because of the separate sets of withs, you'd have to be able to separately compile the private part (it couldn't be required to compile at the same time), so the complications would be doubled (if not more). And compiling a specification is already painful (because of all of the stuff that has to be delayed and fixed up at the end), having to delay that stuff indefinitely would be much worse. I'm think your suggestion could be implemented with enough effort, but it isn't within a country mile of being trivial. Randy.