Multiple Dispatch
John W. Sarkela
sarkela at sbcglobal.net
Mon Jun 16 23:45:12 UTC 2003
Not to mention that this is exactly the case in which an adaptive
optimizing compiler works best. Why not leave this kind of work to an
instrumented runtime and optimizer?
John
On Monday, June 16, 2003, at 11:19 AM, Stephane Ducasse wrote:
> Hi
>
> I think that this the 5% I know where it worked.
> But after this is only my personal experience and I could totally
> wrong. Just pick CLOS or Cecil,
> and try.
>
> Stef
> On Monday, June 16, 2003, at 03:12 PM, daniel.a.joyce at att.net wrote:
>
>> Hmmm?
>>
>> Well, Integer could heavily use multi-methods, as could code I am
>> working on. I
>> find Double Dispatch to be ugly, as it spreads code all throughout
>> classes.
>>
>> <Integer> + <Float>
>>
>> Where Int implements +, and + sends "AddInteger: Integer" to Float so
>> float can
>> get some sort of type information.
>>
>> -Daniel
>>> Hi lex
>>>
>>> I worked with CLOS during 4 years and I did not find the advantage of
>>> multi dispatch.
>>> You know this is like multiple inheritance you need that in 5% of the
>>> case and it
>>> makes the language much more complex for the rest 95%
>>>
>>> Stef
>>
>
More information about the Squeak-dev
mailing list
|