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,6c7dea22b75ba442
X-Google-Attributes: gid103376,public,usenet
X-Google-Language: ENGLISH,ASCII-7-bit
Path: 
 g2news1.google.com!news2.google.com!news.glorb.com!multikabel.net!feed20.multikabel.net!border1.nntp.ams.giganews.com!nntp.giganews.com!feeder3.cambrium.nl!feeder5.cambrium.nl!feed.tweaknews.nl!not-for-mail
From: Ludovic Brenta <ludovic@ludovic-brenta.org>
Newsgroups: comp.lang.ada
Subject: Re: ada compiler?
References: <TYbZi.77377$kj1.12383@bgtnsc04-news.ops.worldnet.att.net>
	<QPednZmRA_Te8KjanZ2dnUVZ_jednZ2d@comcast.com>
	<IooZi.12685$if6.3756@bgtnsc05-news.ops.worldnet.att.net>
	<uklh05-6gt.ln1@newserver.thecreems.com>
	<lvsZi.13247$if6.1368@bgtnsc05-news.ops.worldnet.att.net>
	<1194747665.6151.31.camel@K72> <_evZi.177931$Xa3.50640@attbi_s22>
	<87hcjq46t4.fsf@ludovic-brenta.org>
	<yger6ite2fu.fsf@hugsarin.dmusyd.edu>
	<473abc9d$0$13104$9b4e6d93@newsspool2.arcor-online.net>
	<1195035988.599522.87580@50g2000hsm.googlegroups.com>
	<1195043147.1007.263.camel@kartoffel>
	<1195052954.315227.220840@o3g2000hsb.googlegroups.com>
	<1195056238.1007.317.camel@kartoffel>
	<1195058211.682783.288340@d55g2000hsg.googlegroups.com>
	<1195061973.1007.342.camel@kartoffel>
Date: Wed, 14 Nov 2007 21:40:58 +0100
Message-ID: <87zlxg36hx.fsf@ludovic-brenta.org>
User-Agent: Gnus/5.110006 (No Gnus v0.6) Emacs/21.4 (gnu/linux)
Cancel-Lock: sha1:f8edL8KAktMJZw+9m6K4g7bM53g=
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Organization: Tele2
X-Trace: 
 DXC=]`_VHI2[@mme7SRKlOZGKa6`Y6aWje^YjKEF<T>I=MYdock\QlbT;:eK4cXZGRTNPc<FId6UbK5fg
Xref: g2news1.google.com comp.lang.ada:18391
Date: 2007-11-14T21:40:58+01:00
List-Id: <comp.lang.ada>

Georg Bauhaus writes:
> Heap overflow seems entirely unrelated at first sight, but in
> two ways it needs to be considered here, I think.
>
> First, the -fstack-check warning suggests, in a sense, to use allocators
> and pointers instead of direct objects. When a programmer interprets
> the warning this way and starts using pointers, -f[no]-stack-check
> is likely to affect the structure of his/her Ada program.

No, I don't think -fstack-check suggests changing the program in any
way.  All it does is insert extra run-time checks.  You then convert
stack allocation into heap allocation only if and when necessary.  I
for one almost never use pointers, even in general-purpose
(non-safety-critical) programs because I like to use the scope of
variables to handle memory and accessibility for me.  I see access
values and heap allocation as a necessary evil for dynamic data
structures, and for the occasional very large array that won't fit on
the stack anyway.

-- 
Ludovic Brenta.