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=ham
	autolearn_force=no version=3.4.4
X-Google-Thread: 103376,29d8139471e3f53e
X-Google-NewGroupId: yes
X-Google-Attributes: gida07f3367d7,domainid0,public,usenet
X-Google-Language: ENGLISH,ASCII-7-bit
Path: 
 g2news1.google.com!news3.google.com!feeder.news-service.com!feeder.erje.net!news.internetdienste.de!newsfeed.velia.net!news.tu-darmstadt.de!news.belwue.de!rz.uni-karlsruhe.de!news.gnuher.de!news.enyo.de!not-for-mail
From: Florian Weimer <fw@deneb.enyo.de>
Newsgroups: comp.lang.ada
Subject: Re: Preventing type extensions
Date: Wed, 22 Sep 2010 21:51:16 +0200
Message-ID: <8762xxd0az.fsf@mid.deneb.enyo.de>
References: <87iq2bfenl.fsf@mid.deneb.enyo.de>
	<874odv9npv.fsf@ludovic-brenta.org> <87y6b7cedd.fsf@mid.deneb.enyo.de>
	<66a3704c-54f9-4f04-8860-aa12f516134b@t3g2000vbb.googlegroups.com>
	<87d3sib44t.fsf@mid.deneb.enyo.de>
	<134q4k2ly2pf4$.17nlv1q6q5ivo.dlg@40tude.net>
	<4c8dec8e$0$6990$9b4e6d93@newsspool4.arcor-online.net>
	<epkb3s8dfxk0$.1qdvo5vg2fsgh.dlg@40tude.net>
	<8f6cceFrv2U1@mid.individual.net>
	<135a7dc9-3943-45e4-884b-3cc6bce3db0a@q18g2000vbm.googlegroups.com>
	<i6m45c$gjp$2@news.eternal-september.org>
	<c75a88c5-1d51-4342-904a-743e41adeb7f@k9g2000vbo.googlegroups.com>
	<i7afm3$dn8$1@news.eternal-september.org>
	<a9a93110-c5a1-41cb-b36a-0e8da7f4cacf@q26g2000vbn.googlegroups.com>
	<i7air8$q3k$1@news.eternal-september.org>
	<81799aab-a2e8-4390-8f42-abceaa5fc032@m1g2000vbh.googlegroups.com>
	<i7cd4n$9tj$1@news.eternal-september.org>
	<5c0d7798-ba09-4bd0-a28f-f1b028cce927@y3g2000vbm.googlegroups.com>
	<87r5gl8tky.fsf@ludovic-brenta.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Trace: idssi.enyo.de 1285185076 6023 172.17.135.6 (22 Sep 2010 19:51:16 GMT)
X-Complaints-To: news@enyo.de
Cancel-Lock: sha1:uIR4HoUbyXJIynmk3TX6WXJd58Y=
Xref: g2news1.google.com comp.lang.ada:14193
Date: 2010-09-22T21:51:16+02:00
List-Id: <comp.lang.ada>

* Ludovic Brenta:

> Another area where Ada helps certification is where it distinguishes
> pool-specific from general access types.  C and C++ are both completely
> helpless in this respect.  Consider:
>
> type T_Access is access T'Class; -- no equivalent in C++
> type T_General_Access is access all T'Class; -- equivalent to T* in C++

Iterators are examples of pool-specific allocators in C++.  It's also
common to define your own pointer types in C++.  It's hard to beat the
C++ type system in terms of expressiveness.

> Hey, just a wild idea: how about
>
> type T_Stack_Access is access aliased T;
>
> which indicates that access values of this type can *only* designate
> aliased objects that are on the stack, and never on the heap?

I don't think this would provide useful information.  Tasks blur the
boundary between heap and stack allocation.