From: Tom Emerson <tremerson@gmail.com>
To: Tom Tromey <tromey@redhat.com>
Cc: "Ludovic Courtès" <ludo@gnu.org>, gdb-patches@sourceware.org
Subject: Re: GDB and Guile
Date: Tue, 10 Jul 2012 13:30:00 -0000 [thread overview]
Message-ID: <CAOL6Ehtqe9ehUJqmCeSe-z8UOmzNEmajQz67VZKnz2Xf-TkBoQ@mail.gmail.com> (raw)
In-Reply-To: <87bojok5ez.fsf@fleche.redhat.com>
On Mon, Jul 9, 2012 at 5:09 PM, Tom Tromey <tromey@redhat.com> wrote:
> 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.
I've been working on the assumption (I've only been looking at this in
my spare time for a week or so) that many of the places Guile would
interact with the rest of GDB would be the same as those that Python
uses, which would in turn lead to additional conditionalized or
duplicated functionality that could be abstracted. The suggestion that
there be a 'generic' extension API was motivated by that. If that
isn't a desirable or realistic approach then it is definitely better
not to even consider that path.
Thanks!
-tree
--
Tom Emerson
tremerson@gmail.com
http://www.dreamersrealm.net/tree
next prev parent reply other threads:[~2012-07-10 13:30 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
2012-07-10 13:30 ` Tom Emerson [this message]
[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=CAOL6Ehtqe9ehUJqmCeSe-z8UOmzNEmajQz67VZKnz2Xf-TkBoQ@mail.gmail.com \
--to=tremerson@gmail.com \
--cc=gdb-patches@sourceware.org \
--cc=ludo@gnu.org \
--cc=tromey@redhat.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