Norbert Koch <viteno(a)xemacs.org> wrote:
:-) Okay, so that's settled. Jerry, is there anything I
can/should do
to pave the path?
We have to decide what kind of content the back-to-the-future package
will contain, and how it is structured. Stephen suggested that it
contain forms that cause "you aren't recent enough" errors if older
XEmacsen try to use newer functionality. That's great, but I think we
should provide that newer functionality when possible. That's the
upshot of the request that started this thread.
I propose that the future package contain one future-x.el file for each
x.el file containing a future function. For two of the functions I am
interested in, that would mean a future-subr.el file. We should also
have a core.el or future-core.el file for changes in core. That would
take care of the third function I'm concerned with.
What do you think?
--
Jerry James
http://www.ittc.ku.edu/~james/