From: Andreas Schwab <schwab@linux-m68k.org>
To: Martin Galvan <martin.galvan@tallertechnologies.com>
Cc: gdb-patches@sourceware.org, qiyaoltc@gmail.com, dje@google.com
Subject: Re: [PATCH] testsuite: Remove the unneeded escaping of '[' and ']' characters in test_class_help
Date: Sun, 28 Jun 2015 09:07:00 -0000 [thread overview]
Message-ID: <m2y4j4fbgr.fsf@linux-m68k.org> (raw)
In-Reply-To: <1435464030-22372-1-git-send-email-martin.galvan@tallertechnologies.com> (Martin Galvan's message of "Sun, 28 Jun 2015 01:00:30 -0300")
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.
Andreas.
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
next prev parent reply other threads:[~2015-06-28 9:07 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 [this message]
2015-06-29 14:04 ` Doug Evans
2015-06-29 21:17 ` Martin Galvan
2015-06-29 21:43 ` Doug Evans
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=m2y4j4fbgr.fsf@linux-m68k.org \
--to=schwab@linux-m68k.org \
--cc=dje@google.com \
--cc=gdb-patches@sourceware.org \
--cc=martin.galvan@tallertechnologies.com \
--cc=qiyaoltc@gmail.com \
/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