Re: Disallowing Pre-Defined Operations

[Robert A Duff <bobduff@world.std.com>]

claveman@cod.nosc.mil (Charles H. Sampson) writes:

>      But it doesn't exactly meet my needs, Robert.  I don't even think 
> it's correct to say that it comes close to meeting my needs.

Not having a certain "*" operator seems very close indeed to having it,
but not being allowed to call it.  Yes, it's different in certain cases
that cause ambiguity, but I can't get excited about these rather rare
cases.

>      For all I know, the abstract approach can cause problems other than 
> ambiguities as well.

Well, you have to admit, *that's* a pretty weak argument.  ;-)

>      The behavior of generics is even further away from what I want.

The issue with generics is the same, whether abstract works the way it
does, or the way you would like it to, and whether you spell it
"abstract" or "disllowed" or whatever.  The problem is that inside the
generic, we have this numeric type, and we legally call "*".  Now what
should that do in an instance where there is no "*" (or where there is a
"*" but it's supposed to be illegal to call it)?  Do you have a proposed
solution to that?  I agree that the current Ada solution is less than
satisfactory.

>...  I 
> haven't verified it myself yet, but several people in this thread have 
> said that an abstract operation reverts to non-abstract in a generic 
> instantiation.  For an operation that has been disallowed, there is 
> nothing to revert to.

So what does it do, in your proposal?  You have to give run-time
semantics, or invent some way to make it illegal.

- Bob