Re: [eieio] Modified eieio-method-obarray's obarrays after the first call, and obarray optimisation.

drkm writes:

>   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,

--drkm



-------------------------------------------------------
This SF.Net email is sponsored by the 'Do More With Dual!' webinar happening
July 14 at 8am PDT/11am EDT. We invite you to explore the latest in dual
core and dual graphics technology at this free one hour event hosted by HP,
AMD, and NVIDIA.  To register visit http://www.hp.com/go/dualwebinar