From: David Kastrup <dak@gnu.org>
To: emacs-devel@gnu.org
Subject: Re: Raw string literals in Emacs lisp.
Date: Sun, 27 Jul 2014 15:03:39 +0200 [thread overview]
Message-ID: <871tt7lzro.fsf@fencepost.gnu.org> (raw)
In-Reply-To: 8761ijng08.fsf@uwakimon.sk.tsukuba.ac.jp
"Stephen J. Turnbull" <turnbull@sk.tsukuba.ac.jp> writes:
> Matthew Plant writes:
>
> > Although this data is convincing in some respects, I would like to note
> > that xemacs is dead.
>
> The reports of the death of XEmacs are premature.
>
> > The download off their main page did not even have any
> > raw string literals.
>
> XEmacs 21.4 will never have them.
Drawing the following excerpts from
<URL:http://www.xemacs.org/Releases/index.html>:
Arguably, having the last "stable release" made in 2009, having no
"Gamma release" described as
Note: XEmacs 21.4 has been promoted to stable, and there currently
is no gamma series. Plans for the next release are in the works.
The gamma series of releases is satisfactorily stable for most
sophisticated users. Most Linux or *BSD users should get the best
results from the gamma series, and we strongly recommend it to the
``tester'' distributions like NetBSD current, Debian sid, Mandrake
Cooker, Red Hat Rawhide, and so on. XEmacs will be ready when they
are!
The gamma series of releases is the candidate for promotion to a
stable series. Although we do not promote the code base to gamma
while there are known critical bugs in the code base, to attempt to
meet schedules we also do promote fairly quickly once we've fixed
the last known critical bug. Everybody does this, and everybody
knows that despite the best efforts of the developers, ``point oh''
releases typically still have bugs in them. The gamma concept simply
acknowledges this.
at all slated to become stable, and having the current "Beta release"
branch 21.5 started in 2001 with the description
The beta series of releases is for testers. Users should read the
XEmacs Beta mailing list, <xemacs-beta@xemacs.org>. Users should
prepare themselves for crashes, data loss, freezes, and other
unpleasant events. The beta series contains much experimental code,
and fairly large changes may be introduced directly into the code
base. These are announced as they happen on xemacs-beta. Wannabe
developers may also want to follow the XEmacs Patches
<xemacs-patches@xemacs.org> and XEmacs CVS Commits
<xemacs-cvs@xemacs.org> mailing lists for up-to-the-minute details
about the state of the code base.
is making Debian look like a fast-paced project. Reports of XEmacs
being dead may be exaggerated, but it does look a lot like suspended
animation.
> Sure, you can do a lot for readability as PCRE or Python regexps have
> done, but regexps are unreadable almost by design, and those regexp
> syntaxes benefit from rawstrings, too. Almost anything (that doesn't
> involve changing the meaning of existing legal programs) that improves
> readability of regexps is worthwhile.
>
> Rawstrings are cheap and effective.
When rawstrings are supported, it becomes more expedient to recognize
things like \n and \t, probably also \f in regexps (\b is already
taken). At the current point of time, they just evaluate to n and t.
That makes input of tabs and newlines in raw strings a nuisance and a
potential source of errors.
It's not actually an issue with rawstrings as such, but rather of their
use within regexps.
--
David Kastrup
next prev parent reply other threads:[~2014-07-27 13:03 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-25 19:47 Raw string literals in Emacs lisp Matthew Plant
2014-07-25 19:56 ` Tassilo Horn
2014-07-25 20:06 ` Matthew Plant
2014-07-25 20:15 ` Tassilo Horn
2014-07-25 20:24 ` Matthew Plant
2014-07-25 20:33 ` Tom Tromey
2014-07-25 21:40 ` Matthew Plant
2014-07-26 1:19 ` Stephen J. Turnbull
2014-07-26 5:28 ` Matthew Plant
2014-07-26 5:45 ` chad
2014-07-26 19:39 ` Matthew Plant
2014-07-27 12:27 ` Stephen J. Turnbull
2014-07-27 13:03 ` David Kastrup [this message]
2014-07-27 20:58 ` David Caldwell
2014-07-27 23:17 ` Matthew Plant
2014-07-28 18:27 ` Richard Stallman
2014-07-28 19:32 ` Matthew Plant
2014-07-29 19:15 ` Richard Stallman
2014-07-30 0:26 ` Matthew Plant
2014-07-30 4:28 ` Richard Stallman
2014-07-30 18:54 ` Matthew Plant
2014-07-28 2:16 ` Stephen J. Turnbull
2014-07-28 7:43 ` Andreas Schwab
2014-07-30 20:28 ` Ted Zlatanov
2014-07-30 20:41 ` David Caldwell
2014-07-30 20:54 ` Ted Zlatanov
2014-07-30 21:01 ` Matthew Plant
2014-07-30 21:16 ` Ted Zlatanov
2014-07-30 21:19 ` Matthew Plant
2014-07-31 10:13 ` Ted Zlatanov
2014-08-02 8:47 ` Alan Mackenzie
2014-08-02 9:14 ` David Kastrup
2014-08-02 10:23 ` Alan Mackenzie
2014-08-02 15:51 ` Richard Stallman
2014-08-03 6:50 ` Stephen J. Turnbull
2014-08-03 7:29 ` David Kastrup
2014-08-03 13:12 ` Stephen J. Turnbull
2014-08-03 13:27 ` David Kastrup
2014-08-03 15:01 ` Stephen J. Turnbull
2014-08-04 1:55 ` Richard Stallman
2014-08-04 6:38 ` David Kastrup
2014-08-05 1:41 ` Richard Stallman
2014-08-05 6:15 ` David Kastrup
2014-08-03 13:40 ` David Kastrup
2014-08-03 15:06 ` Stephen J. Turnbull
2014-08-04 1:55 ` Richard Stallman
2014-08-02 9:17 ` Andreas Schwab
2014-07-28 1:29 ` Stephen J. Turnbull
2014-07-26 21:37 ` Thorsten Jolitz
2014-07-29 6:32 ` William Xu
2014-07-29 7:40 ` Andreas Schwab
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=871tt7lzro.fsf@fencepost.gnu.org \
--to=dak@gnu.org \
--cc=emacs-devel@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).