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=-0.3 required=5.0 tests=BAYES_00, REPLYTO_WITHOUT_TO_CC autolearn=no autolearn_force=no version=3.4.4 X-Google-Thread: 103376,dbcfe2b0a74da57e X-Google-Attributes: gid103376,public,usenet X-Google-Language: ENGLISH,ASCII-7-bit Path: g2news2.google.com!news3.google.com!feeder1-2.proxad.net!proxad.net!feeder2-2.proxad.net!npeer.de.kpn-eurorings.net!npeer0.kpn.DE!newsfeed.arcor.de!newsspool4.arcor-online.net!news.arcor.de.POSTED!not-for-mail From: "Dmitry A. Kazakov" Subject: Re: Inherited Methods and such Newsgroups: comp.lang.ada User-Agent: 40tude_Dialog/2.0.15.1 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Reply-To: mailbox@dmitry-kazakov.de Organization: cbb software GmbH References: <1190296353.624737.150940@y42g2000hsy.googlegroups.com> <11m13st1f92kf$.m8s6y8mc8ebk.dlg@40tude.net> <1190321119.206313.65290@57g2000hsv.googlegroups.com> <1190408526.100291.265040@50g2000hsm.googlegroups.com> <9ukf2wtqjs0q$.iuijmal4x56b$.dlg@40tude.net> <1190497995.498679.119190@19g2000hsx.googlegroups.com> <1mw3qju08q8uj.sgzht7ld9ydc$.dlg@40tude.net> <1190579805.451187.71140@d55g2000hsg.googlegroups.com> <1i8ksr774bjbj.vpmnx3c0i9qz.dlg@40tude.net> <1190646125.024072.310020@19g2000hsx.googlegroups.com> <1r9s9v6pcjifl.vp4ktk0unpd1.dlg@40tude.net> <1190753631.240548.101820@19g2000hsx.googlegroups.com> <1190843408.713838.128690@g4g2000hsf.googlegroups.com> <1191012272.457766.273330@57g2000hsv.googlegroups.com> <1191098907.689596.43970@k79g2000hse.googlegroups.com> Date: Sun, 30 Sep 2007 10:38:02 +0200 Message-ID: NNTP-Posting-Date: 30 Sep 2007 10:38:02 CEST NNTP-Posting-Host: 08a0d075.newsspool4.arcor-online.net X-Trace: DXC=WXX=l16WbW\YQ5E:l On Sat, 29 Sep 2007 19:39:47 -0400, Robert A Duff wrote: > One limitation of my example: it doesn't work if the parent > type is abstract. In a from-scratch language design, I think > I would solve that problem by allowing the creation of objects > of abstract type. And constructor functions returns such > objects. But don't allow conversion of such objects to > class-wide (to avoid dispatching (to abstract subprograms)). > What do you think about that? It's not Ada, of course. The black hole of copying non-copyable, returning already existing into itself, now, creating impossible is swallowing the language. (:-)) I think that a construction model of constraint->implementation->unconstrained-thing is semantically cleaner and can work for all types. -- Regards, Dmitry A. Kazakov http://www.dmitry-kazakov.de