From: Michael Snyder <msnyder@cygnus.com>
To: Fernando Nasser <fnasser@cygnus.com>
Cc: "H . J . Lu" <hjl@lucon.org>, gdb-patches@sources.redhat.com
Subject: Re: [PATCH] quoting curly braces in call-rt-st
Date: Wed, 25 Jul 2001 15:35:00 -0000 [thread overview]
Message-ID: <3B5F498B.57E3CD52@cygnus.com> (raw)
In-Reply-To: <3B4A2EB6.99615861@cygnus.com>
Fernando Nasser wrote:
>
> "H . J . Lu" wrote:
> >
> > On Mon, Jul 09, 2001 at 04:37:54PM -0400, Fernando Nasser wrote:
> > > Michael Snyder wrote:
> > > >
> > > > Using double-backslash to quote curly braces in regular expressions
> > > > seems so satisfy the largest subset of versions of expect.
> > > >
> > >
> > > If I understand right, Michael claims his double-backslashed version works with both incarnations of expect regexps. So, we have a perfectly valid pattern which is more robust (works independently of the expect version).
> > >
> > > I think we should make this change anyway.
> > >
> >
> > See
> >
> > http://gcc.gnu.org/ml/gcc-patches/2001-07/msg00034.html
> > http://gcc.gnu.org/ml/gcc-patches/2000-09/msg00353.html
> >
> > H.J.
>
> Thank you H.J.
>
> Folks, we may want to do the same on other test files...
By "do the same", do you mean "use double backslash to quote "{"/"}"?
If so, I agree with you.
next prev parent reply other threads:[~2001-07-25 15:35 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3B411440.1691E1E5@cygnus.com>
2001-07-09 13:37 ` Fernando Nasser
2001-07-09 13:42 ` H . J . Lu
2001-07-09 15:22 ` Fernando Nasser
2001-07-25 15:35 ` Michael Snyder [this message]
2001-07-25 15:41 ` Fernando Nasser
2001-07-25 15:46 ` Michael Snyder
2001-07-07 11:57 Michael Elizabeth Chastain
-- strict thread matches above, loose matches on Subject: below --
2001-07-05 8:34 Michael Elizabeth Chastain
2001-07-05 10:11 ` Andrew Cagney
2001-07-02 18:13 Michael Elizabeth Chastain
2001-07-05 8:09 ` Andrew Cagney
2001-07-05 11:32 ` Michael Snyder
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=3B5F498B.57E3CD52@cygnus.com \
--to=msnyder@cygnus.com \
--cc=fnasser@cygnus.com \
--cc=gdb-patches@sources.redhat.com \
--cc=hjl@lucon.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