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,4e5770c49b971630 X-Google-NewGroupId: yes X-Google-Attributes: gida07f3367d7,domainid0,public,usenet X-Google-Language: ENGLISH,ASCII-7-bit Path: g2news2.google.com!news4.google.com!feeder.news-service.com!news.netcologne.de!newsfeed-fusi2.netcologne.de!newsfeed.straub-nv.de!noris.net!newsfeed.arcor.de!newsspool1.arcor-online.net!news.arcor.de.POSTED!not-for-mail Date: Tue, 03 May 2011 17:22:50 +0200 From: Georg Bauhaus User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.15) Gecko/20110303 Thunderbird/3.1.9 MIME-Version: 1.0 Newsgroups: comp.lang.ada Subject: Re: High-Integrity OO and controlled types References: <679e3217-98dd-43c1-86f6-2038a029c3ea@b19g2000yqg.googlegroups.com> <94f3a272-d071-4a74-bfbd-8f2b4c2347cf@m10g2000yqd.googlegroups.com> <4dbfe6cc$0$7664$9b4e6d93@newsspool1.arcor-online.net> <1in9ypl17vu1t$.1shivr91x8zw6.dlg@40tude.net> In-Reply-To: <1in9ypl17vu1t$.1shivr91x8zw6.dlg@40tude.net> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Message-ID: <4dc01dca$0$6885$9b4e6d93@newsspool2.arcor-online.net> Organization: Arcor NNTP-Posting-Date: 03 May 2011 17:22:50 CEST NNTP-Posting-Host: 7c52672e.newsspool2.arcor-online.net X-Trace: DXC=DS4BjcBg_bR@>[RYkFXOIPA9EHlD;3YcR4Fo<]lROoRQ8kFZLh>_cHTX3j]Dnm_l46\`@P X-Complaints-To: usenet-abuse@arcor.de Xref: g2news2.google.com comp.lang.ada:20113 Date: 2011-05-03T17:22:50+02:00 List-Id: On 03.05.11 14:27, Dmitry A. Kazakov wrote: > On Tue, 03 May 2011 13:28:12 +0200, Georg Bauhaus wrote: > >> On 03.05.11 11:59, Maciej Sobczak wrote: >> >>> Another angle: the fact that the lack of controlled types in HI >>> profiles can be considered as a problem is entirely a result of the >>> fact that Ada completely screwed this aspect at the beginning. >>> Controlledness should not be based on tags - it should be a completely >>> orthogonal property of the type, >> >> Actually, in non-flat languages like Ada, scope exit >> actions should be based on scopes, not (just) types, >> as types can effectively span multiple scopes. > > But typed languages tend to consider actions as operations defined on > types, with certain contracts, reusable, clearly bound effects etc. > > Actions as amorphous chunks of code tossed here and there depending on > scope is a way different ["anisotropic"] approach. In particular it does > not fit into safe modular software design, because of this "anisotropy". What will type-object/module code look like if it is equivalent to its nested analog? Better? My guess is that to achieve the necessary linking, one passes Italian food handles to constructors and/or established registries that receive "events" like "a scope X has been left". In general, would the type-object/module approach work better? For example, assuming something like the naturally nested Integrate function.