From: Tom Tromey <tromey@redhat.com>
To: Tom Emerson <tremerson@gmail.com>
Cc: "Ludovic Courtès" <ludo@gnu.org>, gdb-patches@sourceware.org
Subject: Re: GDB and Guile
Date: Mon, 09 Jul 2012 21:10:00 -0000 [thread overview]
Message-ID: <87bojok5ez.fsf@fleche.redhat.com> (raw)
In-Reply-To: <CAOL6EhuRQ8OqkOvKRVwXpfhG=5kzEDDrOD-Yzk1pChS7c8WVHA@mail.gmail.com> (Tom Emerson's message of "Mon, 9 Jul 2012 16:35:18 -0400")
Tom> Parity with the Python functionality is obviously the first order
Tom> of business, which in turn speaks to generalizing the interface
Tom> between GDB and Python so that it is more (extension language)
Tom> neutral.
It depends on what exactly you mean here, but to I don't think we want
any kind of generic extension API. I think the way that gdb is exposed
to Python has to be ad hoc, and for good reason -- we want control over
API evolution as seen by Python to a degree that we actively don't want
internally.
If you can give more details on what you plan I can give better
feedback. I just didn't want you to set off down a bad path.
Tom
next prev parent reply other threads:[~2012-07-09 21:10 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-28 15:09 Tom Emerson
2012-06-28 19:41 ` Doug Evans
2012-07-09 16:20 ` Ludovic Courtès
2012-07-09 20:35 ` Tom Emerson
2012-07-09 21:10 ` Tom Tromey [this message]
2012-07-10 13:30 ` Tom Emerson
[not found] <20120109032350.GJ2716@adacore.com>
2012-01-09 4:33 ` Andrey Smirnov
2012-01-09 16:24 ` Tom Tromey
[not found] ` <CA+jSXqa_SgOaNscr48FPiab5Tt+p2dJoD1A6B2Qbzbf3uXJs0g@mail.gmail.com>
2012-01-10 4:32 ` Joel Brobecker
2012-01-11 0:18 ` Jiang Jilin
2012-01-11 3:10 ` Mike Frysinger
2012-01-11 3:25 ` Joel Brobecker
2012-01-11 9:48 ` Mark Kettenis
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=87bojok5ez.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=ludo@gnu.org \
--cc=tremerson@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).