Re: To CLOS or not to CLOS?

> 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.

I'm not sure what this would be.  You can create generic functions in CLOS that
require only the object selector and one argument (mimicking a one-argument method
in a traditional OO system), using internal object state for all other entries.

I think CLOS gives you a more nuanced method call hierarchy, because you
can specialize on the combination of arguments that isn't easy to replicate
in C++/Java.

-Brent