From: Tom Tromey <tromey@adacore.com>
To: Simon Marchi <simark@simark.ca>
Cc: Tom Tromey <tromey@adacore.com>,
GDB Administrator <gdbadmin@sourceware.org>,
gdb-patches@sourceware.org
Subject: Re: New ARI warning Wed Oct 2 01:56:22 UTC 2019
Date: Wed, 02 Oct 2019 17:35:00 -0000 [thread overview]
Message-ID: <87zhijt5i5.fsf@tromey.com> (raw)
In-Reply-To: <dc40ec1b-5702-99ac-7cef-7322086255bf@simark.ca> (Simon Marchi's message of "Wed, 2 Oct 2019 13:30:05 -0400")
>>>>> "Simon" == Simon Marchi <simark@simark.ca> writes:
>> +/%p[^][sF]/ && !/%prec/ {
Simon> My mind is a bit confused by that regex: aren't the [^] and [sF] considered
Simon> as two successive character sets? If so, the caret character, which negates
Simon> the character set, applies to nothing.
I believe that in most regexp syntax, a "]" doesn't need to be quoted in
a character class, provided it is either the first character (like
"[]...]") or comes immediately after the "^" (like "[^]...]").
The gawk manual mentions this, though it does also recommend using
backslash, so maybe I should just do that.
(info "(gawk) Bracket Expressions")
To include one of the characters '\', ']', '-', or '^' in a bracket
expression, put a '\' in front of it. For example:
[d\]]
matches either 'd' or ']'. Additionally, if you place ']' right after
the opening '[', the closing bracket is treated as one of the characters
to be matched.
Tom
next prev parent reply other threads:[~2019-10-02 17:35 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-02 1:56 GDB Administrator
2019-10-02 2:50 ` Simon Marchi
2019-10-02 16:15 ` Tom Tromey
2019-10-02 17:02 ` Eli Zaretskii
2019-10-02 17:20 ` Tom Tromey
2019-10-02 17:30 ` Simon Marchi
2019-10-02 17:35 ` Tom Tromey [this message]
2019-10-02 17:39 ` Simon Marchi
2019-10-02 17:45 ` Tom Tromey
2019-10-08 17:16 ` Tom Tromey
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=87zhijt5i5.fsf@tromey.com \
--to=tromey@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=gdbadmin@sourceware.org \
--cc=simark@simark.ca \
/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