From: Doug Evans <dje@google.com>
To: Martin Galvan <martin.galvan@tallertechnologies.com>
Cc: Andreas Schwab <schwab@linux-m68k.org>,
gdb-patches <gdb-patches@sourceware.org>,
Yao Qi <qiyaoltc@gmail.com>
Subject: Re: [PATCH] testsuite: Remove the unneeded escaping of '[' and ']' characters in test_class_help
Date: Mon, 29 Jun 2015 21:43:00 -0000 [thread overview]
Message-ID: <CADPb22SsphX11f5qbYo_W2BO6d2+X0teYhi5yNE1GL22mOVhYw@mail.gmail.com> (raw)
In-Reply-To: <CAOKbPbb2CmhSCb+jA_uDKn01mB2CBr1H+k-vGbk2ROHD5a7FPA@mail.gmail.com>
It is ok to commit as is.
On Mon, Jun 29, 2015 at 4:16 PM, Martin Galvan
<martin.galvan@tallertechnologies.com> wrote:
> Is it ok to commit as it is, or should I change the comment to reflect
> what Andreas said?
>
> On Mon, Jun 29, 2015 at 11:03 AM, Doug Evans <dje@google.com> wrote:
>> On Sun, Jun 28, 2015 at 4:07 AM, Andreas Schwab <schwab@linux-m68k.org> wrote:
>>> Martin Galvan <martin.galvan@tallertechnologies.com> writes:
>>>
>>>> +# Notice that the '[' and ']' characters don't need to be escaped for strings
>>>> +# wrapped in {} braces.
>>>
>>> This isn't true in general, it's because this is a tcl list. The
>>> backslashes are removed when the list is passed through join in
>>> help_test_raw (which removes one level of quoting, but doesn't do
>>> command or variable expansion). But that also means that the backslash
>>> before '.' is ineffective and should be replaced by a double backslash.
>>> Alternatively, each element could be enclosed with braces which disables
>>> any quoting inside it.
>>>
>>>> proc test_class_help { command_class expected_initial_lines args } {
>>>> set l_stock_body {
>>>> - "List of commands\:.*\[\r\n\]+"
>>>> - "Type \"help\" followed by command name for full documentation\.\[\r\n\]+"
>>>> - "Type \"apropos word\" to search for commands related to \"word\"\.[\r\n\]+"
>>>> + "List of commands\:.*[\r\n]+"
>>>
>>> The backslash before ':' is useless.
>>
>> Thanks for the clarity.
>> We don't have to fix all issues in this patch, so the patch is fine with me.
>
>
>
> --
>
>
> Martin Galvan
>
> Software Engineer
>
> Taller Technologies Argentina
>
>
> San Lorenzo 47, 3rd Floor, Office 5
>
> Córdoba, Argentina
>
> Phone: 54 351 4217888 / +54 351 4218211
next prev parent reply other threads:[~2015-06-29 21:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-28 4:01 Martin Galvan
2015-06-28 9:07 ` Andreas Schwab
2015-06-29 14:04 ` Doug Evans
2015-06-29 21:17 ` Martin Galvan
2015-06-29 21:43 ` Doug Evans [this message]
2015-06-30 21:28 ` Martin Galvan
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=CADPb22SsphX11f5qbYo_W2BO6d2+X0teYhi5yNE1GL22mOVhYw@mail.gmail.com \
--to=dje@google.com \
--cc=gdb-patches@sourceware.org \
--cc=martin.galvan@tallertechnologies.com \
--cc=qiyaoltc@gmail.com \
--cc=schwab@linux-m68k.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).