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: 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!npeer01.iad.highwinds-media.com!news.highwinds-media.com!feed-me.highwinds-media.com!post02.iad.highwinds-media.com!news.flashnewsgroups.com-b7.4zTQh5tI3A!not-for-mail
Newsgroups: comp.lang.ada
Subject: Re: Types,
 packages & objects : the good old naming conventions question (without
 religious ware)
References: 
 <561e0a4a-c6c0-42db-9f31-a70f4eae1ed9@a21g2000yqc.googlegroups.com>
 <hce79b$daf$1@aioe.org> <ygeocnohy02.fsf@hugsarin.sparre-andersen.dk>
 <u4ope4pqa.fsf@stephe-leake.org>
 <Xns9CB636112C917pcc482719gmailcom@198.186.192.137>
 <u1vkdrert.fsf@stephe-leake.org> <5vzuqtkwuhwy$.21swwhszn06r.dlg@40tude.net>
 <4af29192$0$26348$4f793bc4@news.tdc.fi>
From: Stephen Leake <stephen_leake@stephe-leake.org>
Date: Fri, 06 Nov 2009 04:54:46 -0500
Message-ID: <u1vkcou55.fsf@stephe-leake.org>
User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.2 (windows-nt)
Cancel-Lock: sha1:dhcMvKRLbG/IE3S1e89JjF7uKgI=
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Complaints-To: abuse@flashnewsgroups.com
Organization: FlashNewsgroups.com
X-Trace: 41a184af3f246e197caa703951
Xref: g2news2.google.com comp.lang.ada:9007
Date: 2009-11-06T04:54:46-05:00
List-Id: <comp.lang.ada>

Niklas Holsti <niklas.holsti@tidorum.invalid> writes:

> 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.

The definition of "backward compatible" is "all existing legal
programs will still be legal".

This ambiguity does not exist in existing legal programs.

It is a good reason not to have separate name spaces; how would we
resolve the ambiguity?

-- 
-- Stephe