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!postnews.google.com!o3g2000hsb.googlegroups.com!not-for-mail From: Ludovic Brenta Newsgroups: comp.lang.ada Subject: Re: ada compiler? Date: Wed, 14 Nov 2007 07:09:14 -0800 Organization: http://groups.google.com Message-ID: <1195052954.315227.220840@o3g2000hsb.googlegroups.com> References: <1194747665.6151.31.camel@K72> <_evZi.177931$Xa3.50640@attbi_s22> <87hcjq46t4.fsf@ludovic-brenta.org> <473abc9d$0$13104$9b4e6d93@newsspool2.arcor-online.net> <1195035988.599522.87580@50g2000hsm.googlegroups.com> <1195043147.1007.263.camel@kartoffel> NNTP-Posting-Host: 32.58.34.227 Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" X-Trace: posting.google.com 1195052954 9577 127.0.0.1 (14 Nov 2007 15:09:14 GMT) X-Complaints-To: groups-abuse@google.com NNTP-Posting-Date: Wed, 14 Nov 2007 15:09:14 +0000 (UTC) In-Reply-To: <1195043147.1007.263.camel@kartoffel> User-Agent: G2/1.0 X-HTTP-UserAgent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.1) Gecko/20061204 Firefox/2.0.0.1,gzip(gfe),gzip(gfe) X-HTTP-Via: 1.1 SEVPXS01 Complaints-To: groups-abuse@google.com Injection-Info: o3g2000hsb.googlegroups.com; posting-host=32.58.34.227; posting-account=ps2QrAMAAAA6_jCuRt2JEIpn5Otqf_w0 Xref: g2news1.google.com comp.lang.ada:18374 Date: 2007-11-14T07:09:14-08:00 List-Id: On Nov 14, 1:25 pm, Georg Bauhaus wrote: > On Wed, 2007-11-14 at 02:26 -0800, Ludovic Brenta wrote: > > Also, if a stack overflow results in > > a SEGV (instead of Storage_Error), I don't clearly see the functional > > difference i.e. the stack overflow gets caught either way. > > But who catches? A player in the game (Ada partition), > or someone in the stadium (OS)? But if the stack is exhausted or nearly so (perhaps because the last in a long series of recursive calls raises Storage_Error), chances are high that the exception handler itself will overflow the stack (e.g. passing your string "Hey! You!" to a procedure might itself cause a stack overflow). This, in my view, greatly reduces the benefit of the exception. Also, what if raising the exception requires some stack space? Maybe I should have said that explicitly. -- Ludovic Brenta.