Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Michael Elizabeth Chastain <mec@shout.net>
To: dberlin@dberlin.org
Cc: gdb-patches@sources.redhat.com, mludvig@suse.cz
Subject: Re: [testsuite] gdb.c++/templates.exp
Date: Wed, 09 Jul 2003 15:35:00 -0000	[thread overview]
Message-ID: <200307091535.h69FZgZf024064@duracef.shout.net> (raw)

Hi Daniel,

mec>   \\(unsigned ?(long|)\\);
mec>
mec> It would accept 'unsignedlong' which would be wrong.

berlin> It shouldn't, unless the regex isn't whitespace sensitive

I think you have it backwards:

  PATTERN       TEXT
  'unsigned' -> 'unsigned'
  ' ?'       -> ''
  '(long|)'  -> 'long'

Matches 'unsignedlong'.

Try it with egrep:

  $ egrep 'unsigned ?(long|)'
  unsignedlong
  unsignedlong

Try it with tclsh:

  $ tclsh
  % regexp "unsigned ?(long|)" unsignedlong
  1

mec> Can you try:
mec>
mec>   \\(unsigned( long|)\\);

berlin> Now *this* would accept unsignedlong, unless the regexps in expect are 
berlin> unlike any other system i've seen.
berlin> 
berlin> This is because the alternation would be between " long" and "", *not* 
berlin> "long" and "" (IE your regex would not be equivalent to 
berlin> <space>long|<space>

This accepts either '(unsigned);' or '(unsigned long);'.
It does not accept '(unsignedlong);'.  Try it with egrep or tclsh.
I did.

  $ tclsh
  % regexp "\\(unsigned( long|)\\)" "(unsigned)"
  1
  % regexp "\\(unsigned( long|)\\)" "(unsigned long)"
  1
  % regexp "\\(unsigned( long|)\\)" "(unsignedlong)"
  0

I agree that the alternation is between " long" and "".
These two regular expressions are equivalent:

  \\(unsigned( long|)\\);
  \\((unsigned long|unsigned)\\);

Michael C


             reply	other threads:[~2003-07-09 15:35 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-09 15:35 Michael Elizabeth Chastain [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:50 Michael Elizabeth Chastain
2003-07-09 16:19 ` Daniel Berlin
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=200307091535.h69FZgZf024064@duracef.shout.net \
    --to=mec@shout.net \
    --cc=dberlin@dberlin.org \
    --cc=gdb-patches@sources.redhat.com \
    --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