>>>> Yes, this subroutine is never directly called from C, so placing an
>>>> advice should work just fine.
> I thought coding conventions prevented advising primitives?
Nothing prevents advising primitive functions (advising special forms
is another matter altogether). But primitive functions can be called
from C directly (rather than via looking up the symbols' function cell)
in which case the advice will be ignored.
> I does not look clean to advise `require' here, just for Org.
It's just an experiment (AFAIK).
>> "Check whether a required feature has been shadowed by changing
>> `load-path' after it has been loaded and reload that feature from
>> current load-path in this case."
> I don't understand why we need this.
For the case where Org is installed via package.el rather than by
manually downloading and following some installation instructions.
> For package manager, a slightly more general version of the above (not
> conditionalized on the feature starting with "org" or "ob") could be
> used around the package compilation. I haven't yet tried this, though.
Maybe the better way to do it is for package.el to compare the set of
files of the new package, with the set of currently loaded `features'
and unload the intersection.
Stefan
