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=unavailable autolearn_force=no version=3.4.4 Path: eternal-september.org!reader01.eternal-september.org!reader02.eternal-september.org!news.eternal-september.org!news.eternal-september.org!news.eternal-september.org!feeder.eternal-september.org!feeder.erje.net!eu.feeder.erje.net!xlned.com!feeder1.xlned.com!npeer.de.kpn-eurorings.net!npeer-ng0.de.kpn-eurorings.net!newsfeed.arcor.de!newsspool2.arcor-online.net!news.arcor.de.POSTED!not-for-mail Date: Wed, 28 Aug 2013 13:42:16 +0200 From: "G.B." User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130801 Thunderbird/17.0.8 MIME-Version: 1.0 Newsgroups: comp.lang.ada Subject: Re: Ada advocacy References: <19595886.4450.1332248078686.JavaMail.geo-discussion-forums@vbbfy7> <2012032020582259520-rblove@airmailnet> <12ee9bc5-3bdf-4ac0-b805-5f10b3859ff4@googlegroups.com> <6c58fae4-6c34-4d7a-ab71-e857e55897c0@x6g2000vbj.googlegroups.com> <246849b7-7a53-48a2-8f64-ff6dfb2086ce@googlegroups.com> <521dbbbb$0$9520$9b4e6d93@newsspool1.arcor-online.net> <1spiuuuxfwqq4$.46v46qs98684.dlg@40tude.net> In-Reply-To: <1spiuuuxfwqq4$.46v46qs98684.dlg@40tude.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Message-ID: <521de20d$0$9507$9b4e6d93@newsspool1.arcor-online.net> Organization: Arcor NNTP-Posting-Date: 28 Aug 2013 13:42:05 CEST NNTP-Posting-Host: 92d2c8ca.newsspool1.arcor-online.net X-Trace: DXC=haOF_:\chnNX36K@\WTHGJic==]BZ:afN4Fo<]lROoRAnkgeX?EC@@@[A^MO;>XjJGnc\616M64>JLh>_cHTX3jMfnEDe`VS8h@ X-Complaints-To: usenet-abuse@arcor.de Xref: news.eternal-september.org comp.lang.ada:17013 Date: 2013-08-28T13:42:05+02:00 List-Id: On 28.08.13 11:42, Dmitry A. Kazakov wrote: > The point Maciej does is valid and it is the issue which prevents tasks > from having entries proper methods supporting inheritance and overriding. If that was the point, there still there is a huge difference between "normal" types with overriding and all on the one hand and task types on the other, namely that task types specify possible orders of method execution (*) That's the deal, a reference to an order of events in time, right in the type. Something that ordinary types don't have. (Except in the manner of trivial sequentiality of method bodies.) I suggest that saying "refactoring" is a far cry from being a satisfactory solution of (*) from the language point of view.