>>>> "R" == rendhalver
<rendhalver(a)xemacs.org> writes:
R> just downloaded all the stuff on that page i think we need to
R> put them all into a c mode somewhere near us
We don't "need" any junk code. It's good to set it up as packages,
but if it's not ready for prime time, we shouldn't put too much effort
into maintaining it. I'd like to see us get in touch with the
authors, see if they're willing to maintain their code as XEmacs
packages. Give them commit privileges as appropriate. Offer them
bug-reporting addresses (somebody remind me to update aliases-xemacs
at tux...).
What we (XEmacs) should do is document these packages in some place
users will see it. Evaluate them, at least to the extent of saying
whether they look like they'll make it out of contrib before we
release 22.0. :-)
R> appreciated then we can include this stuff in cc-mode :)
Make a separate package, only put it in cc-mode when the cc-mode
people say it's OK. In general separate packages for separate
maintainers or separate functionality is a good thing. This is
especially important with packages that are actively maintained
upstream.
--
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