André Thieme wrote: [...] > What do you mean with "encapsulation" in this context?
Presumably that CLOS makes no attempt to enforce the distinction between "private" and "public" methods or class slots. I suppose you can indicate that certain classes, generic functions et c. are "private" by not exporting the symbols associated with them from the relevant package, but even then you merely have a way to communicate your intent to the user, not a way to force them to keep their hands off. ISTR that it's easy to get at "private" things in Python, too, so I'd be surprised if this were a make-or-break issue for Pythonistas. Cheers, Pillsy -- http://mail.python.org/mailman/listinfo/python-list
