Re: replace-match: GNU vs XEmacs
Darryl Okahata <darrylo(a)sr.hp.com> writes:
The best solution is would be to shift the XEmacs-specific option
over once place (make it the sixth option),
Would it really be the best solution?
XEmacs accepted that option long before FSF introduced their own
extension. The extension existed, and people would have used it. By
removing it or tossing it around, I'm afraid we send a "fuck you" note
to those of our users who actually care to use our extensions.
From a different point of view, XEmacs is already full of the BUFFER
arguments to various functions, where appropriate and otherwise.
Those arguments are mostly harmless, but they only work well when they
come last. This makes such functions harder to extend, as witnessed
by this change.
An ugly, kludgy solution would be to test the type of the fifth
parameter;
That's what I did for `buffer-string'; however, I did it only because
the FSF version really made more sense. And yet, even with the
compatibility fix, my solution broke in some cases and had to be fixed
by wmperry.