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: a07f3367d7,25d835bb9a4a003f X-Google-Attributes: gida07f3367d7,public,usenet X-Google-NewGroupId: yes X-Google-Language: ENGLISH,ASCII-7-bit Path: g2news2.google.com!news1.google.com!npeer02.iad.highwinds-media.com!news.highwinds-media.com!feed-me.highwinds-media.com!nx01.iad01.newshosting.com!newshosting.com!83.128.0.12.MISMATCH!news-out2.kabelfoon.nl!newsfeed.kabelfoon.nl!bandi.nntp.kabelfoon.nl!newsfeed.freenet.de!news.teledata-fn.de!newsfeed.arcor.de!newsspool1.arcor-online.net!news.arcor.de.POSTED!not-for-mail From: "Dmitry A. Kazakov" Subject: Re: Types, packages & objects : the good old naming conventions question (without religious ware) 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: <561e0a4a-c6c0-42db-9f31-a70f4eae1ed9@a21g2000yqc.googlegroups.com> <5vzuqtkwuhwy$.21swwhszn06r.dlg@40tude.net> <4af29192$0$26348$4f793bc4@news.tdc.fi> Date: Thu, 5 Nov 2009 10:13:04 +0100 Message-ID: NNTP-Posting-Date: 05 Nov 2009 10:13:04 CET NNTP-Posting-Host: 8aa79fa3.newsspool3.arcor-online.net X-Trace: DXC=WDC6F`RRbV985[]]\]T081McF=Q^Z^V384Fo<]lROoR18kF7enW;^6ZC`4IXm65S@:3>?NcL4iLOM9K; X-Complaints-To: usenet-abuse@arcor.de Xref: g2news2.google.com comp.lang.ada:8989 Date: 2009-11-05T10:13:04+01:00 List-Id: On Thu, 05 Nov 2009 10:48:51 +0200, Niklas Holsti wrote: > Dmitry A. Kazakov wrote: > >> Consider it this way, if _Type is felt appropriate then that is >> semantically equivalent to types having a separate name space. The latter >> could be introduced in Ada at any time, being fully backward compatible. > > I'm not sure about the backward compatibility. For one thing, the 'Size > attribute may have a different value for a type and for an object of the > type. This means that given an object declaration "List : List", where > the latter List is a type name, the expression List'Size would be > ambiguous and could have a different value for the object List and the > type List. Yes, it is ambiguous, but backward compatible. Another disadvantage of a separate name space were barring types as first-class objects. I don't know how actual the latter might be. I have no clear opinion on separate name space for types. Clearly if considered, it should be accompanied with the separate name spaces for labels and package names. Further, the problem of what to do with type T_Ptr is access T; type T_Ref is access constant T; type T_Class_Ptr is access T'Class; will remain. -- Regards, Dmitry A. Kazakov http://www.dmitry-kazakov.de