Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Berlin <dberlin@dberlin.org>
To: Michael Elizabeth Chastain <mec@shout.net>
Cc: gdb-patches@sources.redhat.com, mludvig@suse.cz
Subject: Re: [testsuite] gdb.c++/templates.exp
Date: Wed, 09 Jul 2003 16:19:00 -0000	[thread overview]
Message-ID: <149B7D40-B229-11D7-A383-000A95A34564@dberlin.org> (raw)
In-Reply-To: <200307091550.h69Fo0QW024224@duracef.shout.net>


On Wednesday, July 9, 2003, at 11:50 AM, Michael Elizabeth Chastain 
wrote:

> Hi Daniel,
>
>>>   \\(unsigned ?(long|)\\);
>
>> Just to be clear, this regex should accept nothing, "long", "unsigned
>> long", and "unsigned".
>> This may be *wrong*, but it certainly shouldn't accept "unsignedlong".
>> The ? should be applying to "unsigned ", not just the whitespace.
>
> The ? applies to one atom before it.  An atom is just the single
> character ' ', not the whole string 'unsigned '.  So says "Tcl and the
> Tk Toolkit", section 9.3.
>
> It's been that way in Unix regular expressions since the days of 'ed'.
>
> What with the fifty different regular expression implementations out
> there, maybe one of them does behave that way.

Two, actually.

> Not TCL or egrep or perl
> or vim though.
>
Of course, I never bothered to use one of these, i was working with a 
C++ regex engine.

> Michael C


  reply	other threads:[~2003-07-09 16:19 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-09 15:50 Michael Elizabeth Chastain
2003-07-09 16:19 ` Daniel Berlin [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-07-10 14:38 Michael Elizabeth Chastain
2003-07-11  6:45 ` Michal Ludvig
2003-07-09 15:35 Michael Elizabeth Chastain
2003-07-09 15:05 Michael Elizabeth Chastain
2003-07-09 15:16 ` Daniel Berlin
2003-07-09 15:20   ` Daniel Berlin
2003-07-09 15:38     ` Daniel Jacobowitz
2003-07-09 15:43     ` Andreas Schwab
2003-07-10  7:51 ` Michal Ludvig
2003-07-09 13:26 Michal Ludvig

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

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

  git send-email \
    --in-reply-to=149B7D40-B229-11D7-A383-000A95A34564@dberlin.org \
    --to=dberlin@dberlin.org \
    --cc=gdb-patches@sources.redhat.com \
    --cc=mec@shout.net \
    --cc=mludvig@suse.cz \
    /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