Hi Rudi,
I'm now seeing other bugs: There is a Java-level index-out-of-bounds error caused by a call to %set-standard-instance-access somewhere. However, it's pretty hard to figure out where and why that happens, because the Java error message doesn't tell me where in the Lisp code I am. Can you recommend any tricks how to localize errors better?
I could also make the Closer to MOP changes already available and tell you which test programs cause the problem, in case you would like to take a look at this yourself. Just let me know.
Just a minor thing: Sometimes, you have to declare keyword arguments in CLOS methods just to tell CLOS that a specific keyword argument is acceptable, even if it is not used (see 7.6.5 in the HyperSpec). ABCL gives style-warnings in such cases, but I don't think that should happen…
Best, Pascal
On 25 Aug 2012, at 23:21, Rudolf Schlatte rudi@constantly.at wrote:
On Aug 19, 2012, at 17:49, Pascal Costanza pc@p-cos.net wrote:
Hi Rudi,
I'm currently looking into adding support for ABCL 1.1 to the Closer project. I'm not only adding the support for Closer to MOP itself, but I'm also testing whether the other packages work (like ContextL, etc.).
I found a bug with regard to the slot layout of metaobject classes. It seems that fixed slot positions are assumed where this shouldn't be the case. Here is a transcript that illustrates the problem:
Hi Pascal,
Thanks for the report and diagnosis! This (and a related bug reported by Stas Boukarev) are hopefully fixed in svn.
Slot objects are allocated deep in Java-land (see SlotDefinition.java resp. clos.lisp:make-(direct|effective)-slot-definition for boring details) and the accessors defined in the SlotDefinition class used to believe they know everything about the layout of slot objects. r14134 adds code paths for normal standard-object slot definitions.
Thanks again,
Rudi
closer-devel mailing list closer-devel@common-lisp.net http://lists.common-lisp.net/cgi-bin/mailman/listinfo/closer-devel
-- Pascal Costanza