This is the mail archive of the gdb-patches@sourceware.org mailing list for the GDB project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: GDB and Guile

From: Tom Tromey <tromey at redhat dot com>
To: Tom Emerson <tremerson at gmail dot com>
Cc: Ludovic CourtÃs <ludo at gnu dot org>, gdb-patches at sourceware dot org
Date: Mon, 09 Jul 2012 15:09:40 -0600
Subject: Re: GDB and Guile
References: <CAOL6EhtNKDwKq3M56SLN_BpiyvE+1J4GvjS0E165cXSTMXk4yQ@mail.gmail.com> <87y5msdhzz.fsf@gnu.org> <CAOL6EhuRQ8OqkOvKRVwXpfhG=5kzEDDrOD-Yzk1pChS7c8WVHA@mail.gmail.com>

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

Follow-Ups:
- Re: GDB and Guile
  - From: Tom Emerson

References:
- Re: GDB and Guile
  - From: Ludovic Courtès
- Re: GDB and Guile
  - From: Tom Emerson

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]