From: Tom Tromey <tom@tromey.com>
To: Andrew Burgess <andrew.burgess@embecosm.com>
Cc: Joel Brobecker <brobecker@adacore.com>,
Paul Koning <paulkoning@comcast.net>,
Tom Tromey <tom@tromey.com>,
gdb@sourceware.org
Subject: Re: Proposal to remove Python 2 support
Date: Thu, 17 Sep 2020 11:07:41 -0600 [thread overview]
Message-ID: <87lfh872n6.fsf@tromey.com> (raw)
In-Reply-To: <20200916153400.GC3030@embecosm.com> (Andrew Burgess's message of "Wed, 16 Sep 2020 16:34:00 +0100")
>>>>> "Andrew" == Andrew Burgess <andrew.burgess@embecosm.com> writes:
Andrew> Something that I think might be related here, or at least worth
Andrew> mentioning, is guile support.
Andrew> Without knowing (a) what the new feature is, or (b) how Tom plans to
Andrew> implement...
Andrew> Can the feature be added to guile in the same super clean / clever
Andrew> way? If not are we taking the position that this feature just
Andrew> wouldn't be available on guile? Or would we potentially end up
Andrew> implementing the feature the "other way" anyway?
Normally features are added to the Python or Guile layer based on
developer interest. So, they aren't really at parity in general.
I don't really know if Guile has anything that Python is missing. Maybe
something to do with I/O -- I'm not super familiar with it.
But IIRC Guile doesn't have frame filters, unwinder support, or TUI
windows. Maybe more is missing there as well.
I don't know if inferior control can be added to the Guile layer easily,
but I would assume so, because Scheme generally has better support for
continuation-like things than other languages.
Andrew> Additionally there's always the option of supporting a particular
Andrew> feature only when the user compiles against a particular Python
Andrew> version. I guess this would depend on how tightly coupled the feature
Andrew> ends up being to the rest of the GDB/Python code.
I don't really like to do this kind of thing because the user experience
is bad -- gdb might or might not work. Though of course we're already
in that situation since the entire scripting layer is optional.
Tom
next prev parent reply other threads:[~2020-09-17 17:07 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-15 20:46 Tom Tromey
2020-09-15 20:58 ` Paul Koning
2020-09-15 22:54 ` Re[2]: " fedor_qd
2020-09-16 13:00 ` Joel Brobecker
2020-09-16 13:53 ` Andrew Burgess
2020-09-16 15:03 ` Paul Koning
2020-09-16 15:23 ` Joel Brobecker
2020-09-16 15:34 ` Andrew Burgess
2020-09-17 17:07 ` Tom Tromey [this message]
2020-09-17 17:49 ` Joel Brobecker
2020-09-17 18:03 ` Eli Zaretskii
2020-09-17 18:10 ` Jan Kratochvil
2020-09-17 18:45 ` Eli Zaretskii
2020-09-18 7:15 ` vincent Dupaquis
2020-09-18 7:25 ` Eli Zaretskii
2020-09-17 18:16 ` Joel Brobecker
2020-09-16 15:44 ` Eli Zaretskii
2020-09-16 17:50 ` André Pönitz
2020-09-17 17:03 ` Tom Tromey
2020-09-18 15:59 ` Pedro Alves
2020-09-18 16:39 ` Mikhail.Terekhov
2020-09-18 16:55 ` Tom Tromey
2020-09-18 17:13 ` Mikhail.Terekhov
2020-09-18 17:35 ` Pedro Alves
2020-09-18 19:20 ` Jeffrey Walton
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=87lfh872n6.fsf@tromey.com \
--to=tom@tromey.com \
--cc=andrew.burgess@embecosm.com \
--cc=brobecker@adacore.com \
--cc=gdb@sourceware.org \
--cc=paulkoning@comcast.net \
/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).