Re: To CLOS or not to CLOS?

> I think if Graham spent a good chunk of time working on a CLOS project
> that he, too, would come around to the point of view that CLOS is a
> significant achievement.

    I can agree with all of the good things you say about CLOS; but the
interesting (to me) bit is, what could be done better?  For example:

- Are generic functions really the right or only way to go?  It seems many
of CLOS's advantages could still be had in a object-dispatched object
system designed with a similar mentality, and perhaps there are advantages
to object-dispatch.

- Is the syntax and verbosity really as simple as can be without
sacrificing functionality?

    For example, someone mentioned passing state in method calls that in
an OO system would be stored in the object.  That seems like a strike
against generic-based OO (GOO?).  This issue references both points
above.

- Other things I missed that experienced CLOS users would criticize or
improve if they could?