[armedbear-devel] Patch: convert method-combination from structure to class representation

[Mark Evenson]

Would you mind writing a short Markdown document describing which direction you propose to take the CLOS/MOP subsystems?   See the [Pathname extension proposal][pathname.markdown] for an example of the informal nature of such a document. Obviously, an efficient implementation of CLOS with AMOP would be the ultimate goal, but we need to plan the steps to this point.

[pathname.markdown]: http://code.google.com/p/abcl-dynamic-install/source/browse/doc/design/pathnames/url-pathnames.markdown

Currently, you seem to be implementing things in Java that I think could plausibly cast as CLOS objects themselves, but I am unclear at where this dividing line stands exactly.  Do you have a heuristic for determining things?  I'd love to talk about your rationale etc.

As for code style, as Ville mentions, adopt local code style as much as possible.  By personal bias in coming from the days of connecting to hosts over 1200 baud is a 80x25 window, so I try to get it down to two space where I can get away with out, for which entirely new code (such as EqualSpecializerObject) is "fair game".  I'll comment more on this in reply to Ville's points in the near future.

[1]: http://code.google.com/p/abcl-dynamic-install/source/browse/src/org/armedbear/lisp/EqualSpecializerObject.java

Excited to finally slay CLOSER-MOP!

[Will take a bit of time to test the patches, but they look good.  Stay tuned.]