From: Daniel Jacobowitz <drow@mvista.com>
To: Daniel Berlin <dberlin@dberlin.org>
Cc: Michael Elizabeth Chastain <mec@shout.net>,
gdb-patches@sources.redhat.com, mludvig@suse.cz
Subject: Re: [testsuite] gdb.c++/templates.exp
Date: Wed, 09 Jul 2003 15:38:00 -0000 [thread overview]
Message-ID: <20030709153811.GA19723@nevyn.them.org> (raw)
In-Reply-To: <D1ACF259-B220-11D7-BADE-000A95A34564@dberlin.org>
On Wed, Jul 09, 2003 at 11:20:05AM -0400, Daniel Berlin wrote:
>
> On Wednesday, July 9, 2003, at 11:15 AM, Daniel Berlin wrote:
>
> >
> >On Wednesday, July 9, 2003, at 11:05 AM, Michael Elizabeth Chastain
> >wrote:
> >
> >>Hi Michal,
> >>
> >>This part is not quite correct:
> >>
> >> \\(unsigned ?(long|)\\);
> >>
> >>It would accept 'unsignedlong' which would be wrong.
> >
> >It shouldn't, unless the regex isn't whitespace sensitive
>
> 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.
I have never encountered a regex engine which worked that way. Unless
you parenthesize the ? will only apply to the previous character. At
least perl, TCL, and egrep are (for once!) consistent here. So is
procmail :P
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2003-07-09 15:38 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
2003-07-09 15:43 ` Andreas Schwab
2003-07-10 7:51 ` Michal Ludvig
-- 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:50 Michael Elizabeth Chastain
2003-07-09 16:19 ` Daniel Berlin
2003-07-09 15:35 Michael Elizabeth Chastain
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=20030709153811.GA19723@nevyn.them.org \
--to=drow@mvista.com \
--cc=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