Re: go-lang

Because I made it so. I used the mode to be a vehicle for introducing features from GNU that would be in line with making our APIs more compatible with GNU. (Which is a long term goal.) This might also help in making other packages work. But I also like this approach because of my own shortcomings. I have limited knowledge about XEmacs internals so that learning 21.5 is enough. Having to consider 21.4 during migration makes the task much harder. I haven't used 21.4 for many years. I must also confess that I'm totally ignorant about the future support for 21.4. Not because I don't like 21.4 but I can't understand how we shall be able to merge with upstream packages without breaking it for 21.4 over and over again. I also think it will be time consuming to test on two platforms and quality will suffer because of limited testing on one or the other. Can we afford that with our limited resources? So I think the whole idea of carefully migrating to not keep 21.4 broken is broken. We moved to GPLv3 in order to be able to merge with upstream GPLv3 packages that we really want and need but those will very, very likely break 21.4!? And last but not least it is more fun to move forward. So it is more motivating to make 21.5 better. Having said that... It is probably possible given enough time and effort to back port it to 21.4. It is the use of shell-command-on-region and the syntax-ppss and friends that needs to be adopted to 21.4. Yours -- %% Mats _______________________________________________ XEmacs-Beta mailing list XEmacs-Beta(a)xemacs.org http://lists.xemacs.org/mailman/listinfo/xemacs-beta