unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: Matt Wette <matthew.wette@verizon.net>
To: guile-user@gnu.org
Subject: Re: regex-case
Date: Sat, 06 Feb 2016 14:42:58 -0800	[thread overview]
Message-ID: <3686A109-A3EC-49E3-B206-FE96322B6577@verizon.net> (raw)
In-Reply-To: <87a8ndsjpt.fsf@elektro.pacujo.net>


> On Feb 6, 2016, at 11:49 AM, Marko Rauhamaa <marko@pacujo.net> wrote:

> Only two additions would be needed to make it better:
> 
> [1] Python's named substrings: (?P<name>...)
>     (<URL: https://docs.python.org/3/library/re.html?highlight=regex#reg
>     ular-expression-syntax>)
> 
> [2] Seamless constant string concatenation as in C:
> 
>     #define PREFIX "..."
>     #define MIDDLE "..."
>     #define SUFFIX "..."
>     ...
>     {
>         int status = regcomp(&reg, PREFIX MIDDLE SUFFIX, 0);
>     }
> 

[1] will be tough IMO because it is not supported by the underlying regexp library used by Guile.

[2] may be possible if it is supported by the Guile regexp library.  But I’m not sure there is a clean way to do this, given that syntax-case bindings are lexical.

Matt





  reply	other threads:[~2016-02-06 22:42 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-06 19:13 regex-case Matt Wette
2016-02-06 19:23 ` regex-case Matt Wette
2016-02-06 19:49 ` regex-case Marko Rauhamaa
2016-02-06 22:42   ` Matt Wette [this message]
2016-02-07  8:15     ` regex-case Marko Rauhamaa
2016-02-06 22:10 ` regex-case Matt Wette
2016-02-08 14:29 ` regex-case Ludovic Courtès
2016-02-11  1:19 ` regex-case Matt Wette

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/guile/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3686A109-A3EC-49E3-B206-FE96322B6577@verizon.net \
    --to=matthew.wette@verizon.net \
    --cc=guile-user@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).