This is the mail archive of the gdb@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: Python API questions and use cases

From: Tom Tromey <tromey at redhat dot com>
To: Joel BorggrÃn-Franck <joel dot borggren dot franck at gmail dot com>
Cc: gdb at sourceware dot org
Date: Thu, 16 Sep 2010 13:09:37 -0600
Subject: Re: Python API questions and use cases
References: <AANLkTim24XZssayO6-wvf9WoywRauqXRbUdQi5LjyO9F@mail.gmail.com> <m3iq26x548.fsf@fleche.redhat.com> <AANLkTi=cBL9Cwu5NeX5yVupXwDbam0j3_gXFPGs0WXgz@mail.gmail.com>

>>>>> "Joel" == Joel BorggrÃn-Franck <joel.borggren.franck@gmail.com> writes:

Joel> Ok. I've approached the Python API as a (eventually) complete replacement
Joel> for GDB-script, so whenever I have to use parse_and_eval I feel it's an
Joel> (ugly) hack. This is perhaps not the intention?

We want it to be complete, but there will probably always be some uses
where parse_and_eval is the most convenient thing to do.

We're definitely interested in hearing about holes in the API.
It is fine to just file bug reports as you run across them.

Tom

References:
- Python API questions and use cases
  - From: Joel Borggrén-Franck
- Re: Python API questions and use cases
  - From: Tom Tromey
- Re: Python API questions and use cases
  - From: Joel Borggrén-Franck

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