From: Andreas Schwab <schwab@linux-m68k.org>
To: Tom Tromey <tom@tromey.com>
Cc: Tom de Vries <tdevries@suse.de>, Tom Tromey <tromey@adacore.com>,
gdb-patches@sourceware.org
Subject: Re: [PATCH] Don't nest double quotes in tuiterm.exp
Date: Tue, 09 Sep 2025 21:01:54 +0200 [thread overview]
Message-ID: <87ldmnphzx.fsf@igel.home> (raw)
In-Reply-To: <87ms73pl12.fsf@tromey.com> (Tom Tromey's message of "Tue, 09 Sep 2025 11:56:25 -0600")
On Sep 09 2025, Tom Tromey wrote:
> I wouldn't be overly surprised if I was mistaken about this, but on the
> other hand, nested double-quotes seems quite strange and I'd prefer us
> to avoid it even if it is legal somehow.
There are no nested double quotes in tcl, but a nested command
substitution can contain any valid tcl script, including double quoted
words (Tcl(n) explains this pretty well). This is similar to how
command substitutions are handled in the posix shell (when using $(...))
when they occur in a double quoted context.
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510 2552 DF73 E780 A9DA AEC1
"And now for something completely different."
prev parent reply other threads:[~2025-09-09 19:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-30 18:07 Tom Tromey
2025-07-31 5:16 ` Tom de Vries
2025-09-09 7:18 ` Tom de Vries
2025-09-09 17:56 ` Tom Tromey
2025-09-09 19:01 ` Andreas Schwab [this message]
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=87ldmnphzx.fsf@igel.home \
--to=schwab@linux-m68k.org \
--cc=gdb-patches@sourceware.org \
--cc=tdevries@suse.de \
--cc=tom@tromey.com \
--cc=tromey@adacore.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