[PATCH] Raw strings, from Python via SXEmacs

[Stephen J. Turnbull]

QUERY

Diverting to xemacs-beta.  Evidently SXEmacs has decided to adopt raw
strings, so no point in discussing *there*.  SXEmacs folks are more
than welcome to present their opinions on what XEmacs should do, since
you've probably already discussed some of the points I'm concerned
about.

This introduces a serious backward incompatibility with GNU Emacs and
XEmacs 21.4, without adding functionality beyond an attractive
convenience.  There is a policy question here, and it should be
discussed (including whether we should be more interested in
compatibility with SXEmacs than GNU Emacs!) before committing IMO.

I'm not going to veto (I like raw strings!), but please give it some
time (a couple weeks, rather than the usual 48 hours) before you
conclude that lack of discussion == tacit approval.

>>>>> "Aidan" == Aidan Kehoe <kehoea at parhasard.net> writes:

    Aidan> This patch integrates Martin Kuehl’s raw strings into
    Aidan> XEmacs 21.5,

[In case anybody doesn't know what a raw string is, it's a reader
representation of strings with no escape processing by the reader.
Ie, "\n" does not become a newline internally, it stays as "\n".  This
is very convenient for regexps since you can embed a newline in the
string with little effort, and the regexp "\\(a\\|b\\)" in a normal
string becomes "\(a\|b\)" in a raw string.]


-- 
School of Systems and Information Engineering http://turnbull.sk.tsukuba.ac.jp
University of Tsukuba                    Tennodai 1-1-1 Tsukuba 305-8573 JAPAN
               Ask not how you can "do" free software business;
              ask what your business can "do for" free software.