Of course you are right that it's the superclass and
not the method. I wrote the patch a week ago and
didn't look closely when I posted it. I apologize for
I'm using ASDF so yes, things are compiled.
I have attached a full macroexpansion of the
def-java-class. "operation" appears only twice, once
in the documentation of a DEFUN and once in the
superclass list of the DEFCLASS.
In jfli.lisp, class-symbol is a function (DEFUN) yet
"class-symbol" does not appear in the full
Am I correct in saying that class-symbol is being
called during the expansion of def-java-class, which
occurs at compile-time, but not during the execution
of the expanded code, which occurs at load-time? IIUC,
all of the Java<->Lisp structures must be created anew
at load time (in compiled code) after the JVM has been
Perhaps you can suggest a better fix. However, with my
patch, I can use ASDF and still get my SWT window to
--- Andras Simon <asimon@...> wrote:
> I'm confused.
> |org.eclipse.jface.operation|::IRUNNABLECONTEXT. is
> superclass, not the type of a method argument, isn't
> it? And
> def-java-class constructs the call to defclass like
> `(defclass ,(class-symbol full-class-name)
> ,(mapcar #'class-symbol
> (get-superclass-names full-class-name)) ())
> But class-symbol does call ensure package.
> Are you having this problem when you load a compiled
> file containing a
> def-java-class form into a fresh Lisp image?
Do you Yahoo!?
Yahoo! Mail - 50x more storage than other providers!
Get latest updates about Open Source Projects, Conferences and News.