From: Tom Tromey <tom@tromey.com>
To: "Zaric, Zoran (Zare)" <Zoran.Zaric@amd.com>
Cc: Tom Tromey <tom@tromey.com>,
"gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: [PATCH v2] Replace the symbol needs evaluator with a parser
Date: Thu, 12 Nov 2020 13:03:10 -0700 [thread overview]
Message-ID: <87imaacphd.fsf@tromey.com> (raw)
In-Reply-To: <DM6PR12MB27629B86EB857016F4877516F81D0@DM6PR12MB2762.namprd12.prod.outlook.com> (Zoran Zaric's message of "Thu, 22 Oct 2020 14:58:57 +0000")
Sorry about the delay on my reply here.
>> I've spoken with Pedro Alves and Simon Marchi about this and the difficulty
>> here is that both "python" and "scheme" interfaces expose this functionality
>> to the user.
Yes, I see. That's annoying!
But, it's also hard to see a way out of that mess. So I guess your
approach is the way to go.
I'll reply separately with another question I have.
Tom
next prev parent reply other threads:[~2020-11-12 20:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-07 17:26 Zoran Zaric
2020-10-21 20:35 ` Tom Tromey
2020-10-22 14:58 ` Zaric, Zoran (Zare)
2020-10-27 19:51 ` Pedro Alves
2020-11-12 20:03 ` Tom Tromey [this message]
2020-11-12 20:11 ` Tom Tromey
2020-11-12 21:17 ` Zaric, Zoran (Zare)
2020-11-12 21:29 ` Zaric, Zoran (Zare)
2020-11-30 18:18 ` Zaric, Zoran (Zare)
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=87imaacphd.fsf@tromey.com \
--to=tom@tromey.com \
--cc=Zoran.Zaric@amd.com \
--cc=gdb-patches@sourceware.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).