> Why? There is no positive reason to make =
Emacs module code resemble
> Emacs core code.
Of course, there is.
Which one? Given the overall state of =
the Emacs core code (lots of global mutable state, thread-hostile, lots of =
macros...) I'd rather want modules to be as different from the Emacs co=
re as possible.
The module interface is an interface. No good int=
erface prescribes how its implementations have to look like.=C2=A0