Dan observed: > I hadn't considered having it as a global thing, just because I can see > class Foo wanting multimethods, and class Bar being fine with 'normal' > class hierarchy walking, and class Baz deciding it wants the automatic > redispatch form of method calling. > > We could make it a global thing and have only a single way to dispatch, in > which case it would be lexically overridable, but that seems awfully > limiting... I fully agree that per-class and per-object dispatch control is desirable. But I was also proposing that the *default* dispatch mechanism be user-selectable. Hence a global hook. Damian
- Re: CLOS multiple dispatch Damian Conway
- RE: CLOS multiple dispatch Hong Zhang
- Re: CLOS multiple dispatch Michael G Schwern
- Re: CLOS multiple dispatch Damian Conway
- Re: CLOS multiple dispatch Me
- Re: CLOS multiple dispatch Damian Conway
- Re: CLOS multiple dispatch Dan Sugalski
- RE: CLOS multiple dispatch Hong Zhang
- Re: CLOS multiple dispatch David L. Nicol
- Re: CLOS multiple dispatch David L. Nicol
- RE: CLOS multiple dispatch Damian Conway
- RE: CLOS multiple dispatch Damian Conway
- RE: CLOS multiple dispatch Hong Zhang
- Re: CLOS multiple dispatch Michael G Schwern
- RE: CLOS multiple dispatch Dan Sugalski
- RE: CLOS multiple dispatch Damian Conway
- Re: CLOS multiple dispatch Me
- Re: CLOS multiple dispatch Dan Sugalski
- Re: CLOS multiple dispatch David L. Nicol
- Re: CLOS multiple dispatch David L. Nicol
- RE: CLOS multiple dispatch David Whipp