From: Tom Tromey <tom@tromey.com>
To: Tom de Vries <tdevries@suse.de>
Cc: Tom Tromey <tom@tromey.com>, Hannes Domani <ssbssa@yahoo.de>,
Hannes Domani via Gdb-patches <gdb-patches@sourceware.org>
Subject: Re: [PATCHv2] Restore gdb.SYMBOL_STRUCT_DOMAIN constant
Date: Thu, 10 Jun 2021 12:48:40 -0600 [thread overview]
Message-ID: <87sg1ph7xz.fsf@tromey.com> (raw)
In-Reply-To: <5a314e1b-4cc7-af38-81e9-df4e37e793a8@suse.de> (Tom de Vries's message of "Sun, 6 Jun 2021 00:36:32 +0200")
>>>>> "Tom" == Tom de Vries <tdevries@suse.de> writes:
Tom> Maybe easy enough to warn about in gdb_test_multiple:
Tom> ...
Tom> if { [regexp -line {python print +[^(]} $command] } {
Tom> warning [concat \
Tom> "Missing parentheses in python print command," \
Tom> " will fail with python3"]
Tom> }
Tom> ...
Tom> ?
Tom> Or, even correct automatically:
Tom> ...
Tom> if { [regexp -line {python print +[^(]} $command] } {
Tom> set command [regsub {python print (.*)} $command \
Tom> {python print (\1)}]
Tom> }
Tom> ...
Tom> ?
I find auto-fixing pretty funny somehow, but I feel like it might be
confusing or even bite us someday.
Another way out would be a new proc to wrap "python print" so that it's
just not possible to mess up.
Tom
prev parent reply other threads:[~2021-06-10 18:48 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20210526170536.657-1-ssbssa.ref@yahoo.de>
2021-05-26 17:05 ` Hannes Domani
2021-05-26 18:13 ` Andreas Schwab
2021-05-26 18:19 ` Hannes Domani
2021-05-29 3:19 ` Simon Marchi
2021-06-02 18:39 ` Tom Tromey
2021-06-03 13:00 ` Hannes Domani
2021-06-05 12:27 ` Tom de Vries
2021-06-05 12:43 ` Hannes Domani
2021-06-05 13:57 ` Tom Tromey
2021-06-05 22:36 ` Tom de Vries
2021-06-10 18:48 ` Tom Tromey [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=87sg1ph7xz.fsf@tromey.com \
--to=tom@tromey.com \
--cc=gdb-patches@sourceware.org \
--cc=ssbssa@yahoo.de \
--cc=tdevries@suse.de \
/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).