> Does this mean that the caller of a multimethod has to know he calls a > multimethod (as oposed to a regular method). Should not the user of a > library spared from such implementation details, however sexy they are?
One might well argue the same thing about calling normal subroutines vs methods. Personally, I think you *should* have to be explicit as to whether you're expecting to do single or multiple dispatch, so the compiler can catch those cases where your expectation is at odds with the program's actual semantics. Damian
