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,86c750b8474bf6d5 X-Google-Attributes: gid103376,domainid0,public,usenet X-Google-Language: ENGLISH,ASCII-7-bit Path: g2news1.google.com!news4.google.com!feeder.news-service.com!newsfeed-fusi2.netcologne.de!news.netcologne.de!newsfeed-hp2.netcologne.de!newsfeed.arcor.de!newsspool3.arcor-online.net!news.arcor.de.POSTED!not-for-mail Date: Mon, 09 Jun 2008 11:43:36 +0200 From: Georg Bauhaus User-Agent: Thunderbird 2.0.0.14 (Macintosh/20080421) MIME-Version: 1.0 Newsgroups: comp.lang.ada Subject: Re: About String References: <484ABED3.8040909@obry.net> <484b802a$0$23844$4f793bc4@news.tdc.fi> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Message-ID: <484cfb49$0$6601$9b4e6d93@newsspool2.arcor-online.net> Organization: Arcor NNTP-Posting-Date: 09 Jun 2008 11:43:37 CEST NNTP-Posting-Host: 616cb52b.newsspool2.arcor-online.net X-Trace: DXC=`^WhaYFa4HAI7\_^6>c20JA9EHlD;3YcB4Fo<]lROoRA8kFJLh>_cHTX3jM=VmiMZLk8LA X-Complaints-To: usenet-abuse@arcor.de Xref: g2news1.google.com comp.lang.ada:627 Date: 2008-06-09T11:43:37+02:00 List-Id: Dmitry A. Kazakov schrieb: > On Sun, 08 Jun 2008 17:19:11 -0400, Robert A Duff wrote: > >> Maciej Sobczak writes: >> >>> After all, with the possibility to initialize the new variable with >>> arbitrarily complex expression (including function call), this is >>> already the case and the whole declare-begin-end block is just >>> reflecting some artificial separation. >> I agree. I suppose it comes from Pascal, where declarations and >> executable code are completely separated. It makes no sense in >> Ada, where declarations are just as executable as statements. > > I disagree. I think it does make sense because it clearly defines the scope > of the declared variable. Still, a somewhat *new* kind kind of handling exceptions in single declarations looks interesting? Given linear order of elaboration in declarative parts, and thus the possibility of sequencing initialization of local variables: procedure P is declare X1: constant T; -- like Java final begin X1 := New_T(...); -- may raise CE exception when Constraint_Error => X1 := Fallback_T; -- better than Java final end; X2: D := New_D(X1, ...); -- safely refer to X1 begin ... end P;