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,FREEMAIL_FROM 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!feeder.eternal-september.org!aioe.org!.POSTED!not-for-mail From: Victor Porton Newsgroups: comp.lang.ada Subject: Re: Type invariants and private extensions? Date: Mon, 11 Sep 2017 23:48:43 +0300 Organization: Aioe.org NNTP Server Message-ID: References: <364ff8e0-c7dd-4980-b19f-5d438edd8353@googlegroups.com> NNTP-Posting-Host: qUTqmJlZKcITHxg9FVl9Fw.user.gioia.aioe.org Mime-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 7Bit X-Complaints-To: abuse@aioe.org User-Agent: KNode/4.14.10 X-Notice: Filtered by postfilter v. 0.8.2 Xref: news.eternal-september.org comp.lang.ada:48013 Date: 2017-09-11T23:48:43+03:00 List-Id: Egil H H wrote: > On Monday, September 11, 2017 at 9:51:35 PM UTC+2, Victor Porton wrote: >> As far as I understand, type invariants cannot be applied to types with >> private extensions. Right? >> >> It would be nice to create private extension types which would allow to >> use them only when certain boolean function on the parent type returns >> True. >> >> Is anything like this possible? >> > > You can already do > type Foo is tagged private > with Type_Invariant'Class => Bar(Foo); > > The Invariant will then be inherited by all derived types It is not what I want. I want different invariants for different derived types. -- Victor Porton - http://portonvictor.org