Hi all,<div><br></div><div>In an attempt to solve ticket 201 and everything related (now that I&#39;m into it anyway), I&#39;ve been staring at the failure of one of ABCL&#39;s own tests and can&#39;t seem to understand what&#39;s going on.</div>
<div><br></div><div>So, DMC-TEST-MC.1 is failing because it uses a non-standard METHOD-QUALIFIER. STD-COMPUTE-EFFECTIVE-METHOD throws an error when matching the qualifiers of the defined methods with the method groups and finds that the method combination isn&#39;t one of type long-form. However, the problem is: it really *is* of type long form. However, this seems to happen *only* in the compiled case....s</div>
<div><br></div><div>So, I inserted a trace:</div><div><br></div><div>(eval-when (:compile-toplevel)</div><div>   (trace mop::STD-COMPUTE-EFFECTIVE-METHOD))</div><div><br></div><div>and extracted the test form from outside the test case, in order to be able to see the error triggered (RT just prints #&lt;simple-error &gt;):</div>
<div><br></div><div>(dmc-test-mc.1 :k 1)</div><div><br></div><div>The result is this backtrace:</div><div><br></div><div><div>     [java]   0: (MOP::STD-COMPUTE-EFFECTIVE-METHOD #&lt;STANDARD-GENERIC-FUNCTION DMC-TEST-MC.1 {10D3D99}&gt;</div>
<div>                          #&lt;METHOD-COMBINATION {69B861}&gt; (#&lt;STANDARD-METHOD {C821EF}&gt;))</div></div><div><br></div><div>which clearly shows the method combination is of type METHOD-COMBINATION and not of type LONG-METHOD-COMBINATION.</div>
<div><br></div><div>I do understand that this is the error, but I can&#39;t for the life of me figure out how we get into the situation that the method combination being instantiated is of the resulting type METHOD-COMBINATION...</div>
<div><br></div><div>Any help on debugging or additional insights would be extremely appreciated!</div><div><br></div><div><br></div><div>Bye,</div><div><br></div><div>Erik.</div>