-- "Stephen J. Turnbull" <turnbull(a)sk.tsukuba.ac.jp> spake thusly:
I don't know whether it would have been acceptable to Michael in
the
EFS case or not, but it would have made it possible to temporarily fix
EFS without changing the package. The cost to Michael (AFAICT) would
be the administrative cost of providing the fix symbol in future
versions of EFS. The cost to our users would be (1) we'd have to
require EFS in our update so we can overwrite the function definitions
that need to be fixed and (2) very confusing breakage if somehow the
non-working definitions got reloaded. I think that overhead and the
slight risk of reloading would be worth it _for a temporary, but
urgent, fix_ like that one.
(1) wouldn't even be necessary if eval-after-load were used. This would
probably very much reduce the likelihood of (2) as well.