From: Greg McIntyre <greg@...>
Date: 2003-11-22T07:52:24+09:00
Subject: Re: "stereotyping" (was: Re: Strong Typing (Re: Managing metadata about attribute types) )

"Ara.T.Howard" <ahoward@ngdc.noaa.gov> wrote:
> 6. Interfaces __HAVE__ implementations vs. classes __IMPLEMENTING__ an
> Interface.  this is vastly simpler with respect to backward compat:
> 
>   BAD:
> 
>     class MyClass
>       # requires change to class 'Class'
>       implements Interface
>     end
> 
>   GOOD:
> 
>     interface.impl << MyClass
> 
>     # no change to class 'Class' needed

How does that work? I envisaged that classes would be "tagged" as
implementing a set of interfaces, then that set propagating to objects
created from that class upon instantiation. That way objects too would
be aware of which interfaces they supported to facilitate quicker
parameter type (interface) checking. If it's the Interface object which
keeps a set of supporting classes, doesn't that require a search through
them to find, at the point of instantiation, which interfaces the class
supports?

-- 
Greg McIntyre ======[ greg@puyo.cjb.net ]===[ http://puyo.cjb.net ]===