Just Launched: You can now import projects and releases from Google Code onto SourceForge
We are excited to release new functionality to enable a 1-click import from Google Code onto the Allura platform on SourceForge. You can import tickets, wikis, source, releases, and more with a few simple steps. Read More
> I just see something I don't understand. Calling a generic
> function modifying the eieio-method-obarray's obarrays of this
> generic function.
Ok, I understand. BTW, I made a mistake, because I didn't use
the named constants 'method-static', 'method-before' and so on,
so I misunderstood the modified obarray were for :AFTER
and :STATIC. But they are for :BEFORE and :AFTER.
'eieio-generic-form', which returns the first function to call
(depending on a generic function name, a class name and a
qualifier), creates such a symbol if it doesn't exist yet (for
optimisation, I think). And when we call a primary method, this
function is called for before and after methods too, indeed.
Sorry for disturbing,
> BTW, I don't really understand what is the obarray
> optimisation. Can someone explain it in a few lines?
Ok, I understand. It uses the value cell of the symbol to
point to the next 'fboundp'ed symbol, to can directly access
classes (in the class precedence list) for wich a method was
Is it right?