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.3 required=5.0 tests=BAYES_00,INVALID_MSGID
	autolearn=no autolearn_force=no version=3.4.4
X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: 103376,4ee5611d3fbf05b7
X-Google-Attributes: gid103376,public
From: dewar@merv.cs.nyu.edu (Robert Dewar)
Subject: Re: Enumeration literal visibility and use type
Date: 1998/05/28
Message-ID: <dewar.896386840@merv>#1/1
X-Deja-AN: 357411878
References: <6kej65$dnh$1@hermes.seas.smu.edu|
 <6kejt5$75u@gcsin3.geccs.gecm.com> <6kensr$fqq$1@hermes.seas.smu.edu>
 <6kf0r3$isj$1@mulga.cs.mu.OZ.AU> <6kgh82$92n@gcsin3.geccs.gecm.com>
 <dewar.896294335@merv> <6kj7av$qsn@gcsin3.geccs.gecm.com>
X-Complaints-To: usenet@news.nyu.edu
X-Trace: news.nyu.edu 896386909 1686 (None) 128.122.140.58
Organization: New York University
Newsgroups: comp.lang.ada
Date: 1998-05-28T00:00:00+00:00
List-Id: <comp.lang.ada>


John McCabe said

<<>seems very inconsistent to me. I do understand the use type argument,
>but surely to make it apply to enumeration literals and not other
>primitive operations would be very odd indeed.

I'm not sure what you mean here. Isn't it the primitive operations that
it already applies to? If so, there is no suggestion of it being applied
to only enumeration literals and not to the primitive operations. As far
as I understand it, the question is why doesn't it apply to both?
>>

You are getting confused by the terminology. Primitive operations refers
to all functions and procedures defined with a parameter or return type
of the type. You read "operators" for operations. use type refers ONLY
to operators, not to all primitive operations.