Custom Query (1030 matches)

Of the three general schemes for implementing undo/redo that I can think of - namely:

1. Use the Cocoa text system's built-in support

2. Use an NSUndoManager to track changes to the buffer/textstorage

3. Do it all at the lisp level

I think that either (2) or (3) would be the most attractive.

? (defclass erroneous-class.13 ()
   (a b c)
   (#.(gensym)))
#<STANDARD-CLASS ERRONEOUS-CLASS.13>
? (make-instance 'erroneous-class.13)
#<ERRONEOUS-CLASS.13 #x300044399DDD>
?

The spec says a program-error is required for unsupported options. This may have been augmented by the MOP, I don't know. But in any case, some indication of a problem should be given at some point.

After a little poking about, it seems like the problem is this method:

 (defmethod initialize-instance :before ((class class) &key &allow-other-keys)
  (setf (%class.ctype class) (make-class-ctype class)))

The &allow-other-keys in this method causes keyword arg checking for class objects to be disabled. I wonder it it would be worthwhile (or even allowed) to treat methods that have &allow-other-keys without &rest as not disabling initialization arg checking.

? (defun foo () (eql))
;Compiler warnings :
;   In FOO: In the call to EQL with arguments (),
;     0 arguments were provided, but at least 2 are required
;     by the current global definition of EQL
? (foo)
T
?

Minor, but it would be nice to get a runtime error, in case you miss the compile-time warnings for whatever reason.