>>>> "KY" == Katsumi Yamaoka
KY> Well, I think the XEmacs version of unicode.el should be
KY> renamed to something like mule-unicode.el. This is simply
KY> because the XEmacs version of unicode.el has arrived later in
KY> the world.
It's not the file name that's at issue, it's the feature name. Having
the same file name is just a convenience for require.
Both Emacsen are going in the direction of "native" support for
Unicode, and XEmacs at least will probably go to Unicode for the
internal encoding, possibly for 22.0 (the current devel codebase).
XEmacs Unicode support is independent of Mule, since 21.5.6. So why
shouldn't we use the obvious feature, 'unicode, for the "standard"
KY> ;; Maybe we need Emacs-Lisp-InterNIC. :-p
We have one, have had for many years. It's the convention that a
library picks a unique prefix and uses it for global symbols and
features, while the core has no prefix. The current exceptions are
generally packages that were moved out of core in 21.1.
It would be nice if we had a Common-Lisp-like package system but we
don't. We have to rely on the discipline of library authors.
Institute of Policy and Planning Sciences http://turnbull.sk.tsukuba.ac.jp
University of Tsukuba Tennodai 1-1-1 Tsukuba 305-8573 JAPAN
My nostalgia for Icon makes me forget about any of the bad things. I don't
have much nostalgia for Perl, so its faults I remember. Scott Gilbert c.l.py