unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: David Hansen <david.hansen@gmx.net>
To: help-gnu-emacs@gnu.org
Subject: Re: ELisp: special read syntax for regular expressions?
Date: Tue, 15 Apr 2008 06:24:02 +0200	[thread overview]
Message-ID: <871w57eof1.fsf@localhorst.mine.nu> (raw)
In-Reply-To: fu0p9p$253u$1@agate.berkeley.edu

On Mon, 14 Apr 2008 23:27:53 +0000 (UTC) Ilya Zakharevich wrote:

> [A complimentary Cc of this posting was sent to
> David Hansen 
> <david.hansen@gmx.net>], who wrote in article <mailman.10052.1207428807.18990.help-gnu-emacs@gnu.org>:
>> > I think I know the answer: one needs to allow a special read syntax
>> > for regular expressions (the result being an ordinary string).  This
>> > way one can avoid the acute backslashitis [by inverting \( and (,
>> > etc], the regular expressions may be specially indented, and the
>> > syntax highlighter would have a chance to remove most of the remaining
>> > complexity by proper highlighting (similar to CPerl one).
>> >
>> > What do you think?
>> 
>> Have a look at the Gauche Scheme implementation.  It has a regexp read
>> syntax: #/.../.
>
> IMO, having SLASH hardwired as a delimiter is a silly choice; it makes
> matching a slash harder, UNNECESSARILY.  If one MUST hardwire some
> delimiters, it should better be () (since un-backwacked parens are
> almost guarantied to be matched inside a regular expression, one needs
> no extra backwacking to enclose the REx into MATCHED parens).
>
> Any thoughts?  Is /(REX) prohibited by some considerations?

The lisper will expect a `#' to see that it it's a special read syntax,
and it's probably a good idea to stick with CL conventions/standards[1].

I'd vote for #/<any paren>REX<matching closing>.  But I have to admit
that I don't know anything about the emacs lisp reader.  Maybe the
discussion should be moved to emacs-devel.

David

Footnotes: 
[1]  http://www.lispworks.com/documentation/HyperSpec/Body/02_dh.htm






      parent reply	other threads:[~2008-04-15  4:24 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-05 11:17 ELisp: special read syntax for regular expressions? Ilya Zakharevich
2008-04-05 20:48 ` David Hansen
2008-04-06  3:18 ` Tim X
2008-05-04  1:38   ` David Combs
2008-04-06  9:35 ` Peter Dyballa
     [not found] ` <mailman.10068.1207474538.18990.help-gnu-emacs@gnu.org>
2008-04-06 21:38   ` Ilya Zakharevich
2008-04-12 23:12     ` Peter Dyballa
     [not found]     ` <mailman.10316.1208041979.18990.help-gnu-emacs@gnu.org>
2008-04-12 23:34       ` Ilya Zakharevich
2008-04-12 23:36         ` Ilya Zakharevich
2008-04-09 22:43 ` Mike Mattie
     [not found] ` <mailman.10052.1207428807.18990.help-gnu-emacs@gnu.org>
2008-04-14 23:27   ` Ilya Zakharevich
2008-04-14 23:41     ` Joost Diepenmaat
2008-04-15  1:51       ` Ilya Zakharevich
2008-04-15  4:24     ` David Hansen [this message]

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=871w57eof1.fsf@localhorst.mine.nu \
    --to=david.hansen@gmx.net \
    --cc=help-gnu-emacs@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.
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).