[slime-devel] Making potentially problematic changes
eslick at csail.mit.edu
Thu Jan 26 18:16:52 UTC 2006
I've updated the inspector in swank.lisp to support metaclass based slot-value overrides. This requires use of the mop functions slot-boundp-using-class and slot-value-using-class (and adding them to the swank-mop package) which may not be consistent over the various versions. Since the inspector is rather central to slime, I don't want to commit this change directly (and don't have write permissions to slime CVS (ieslick at common-lisp.net). Is there a proper procedure for testing a change like this if you don't have all the test configurations available locally?
More information about the slime-devel