12:20:59scymtymi have the impression that ABCL does code walking without macro expansion to determine whether the method body contains CALL-NEXT-METHOD calls: https://github.com/armedbear/abcl/blob/bca11a225a64466c785e291d5d01f19fc8c09ac3/src/org/armedbear/lisp/clos.lisp#L2764 am i missing something?
12:22:37scymtym(and indeed, manually macroexpanding a method in McCLIM that "hides" a CALL-NEXT-CALL call in a macro fixes the problem i'm seeing)
12:27:22ShinmeraI wrote a compiler for a proto-java targeting the jvm. Can't say I enjoyed the bytecode much.
12:30:10scymtymshka_: that may also be the case. i'm currently wondering whether there is a bug there. i'm asking because i can't see how this could work correctly