IE> I recall there being problems taking base class injection out of
IE> shared-initialize - can initialize-instance manipulate the class
IE> precedence list and direct superclasses at that point in the instance
IE> initialization?
I think it should work the same way -- INITIALIZE-INSTANCE :aroun
I recall there being problems taking base class injection out of
shared-initialize - can initialize-instance manipulate the class precedence
list and direct superclasses at that point in the instance initialization?
It occurs to me that, the easiest way to fix this is by policy; remove the
func
I also made a change for ccl so we don't inject the class if the dependencies
argument was not provided (vs passing it along as a nil argument). I'll look
at the alternate placement.
AMOP spec says that users shouldn't add methods to SHARED-INITIALIZE of
a metaclass. I think it can be moved
The problem was exposed by loading elephant again without also loading the
backend libraries. I made a few changes so that doesn't happen so easily.
Sounds like you had a better fix. I haven't dug into this code base, nor done
much CL hacking, in almost two years so feeling rusty. :)
I also
IE> Anyone remember why we put this into the elephant.asd file?
IE> (defmethod operation-done-p ((o load-op) (c elephant-c-source)) nil)
To make sure that library is loaded at least once? There is no way to check
whether it is loaded via UFFI.
And if you return T ASDF might skip loading altoge
