This is the mail archive of the
gdb@sourceware.org
mailing list for the GDB project.
Re: Some feedback about the python scripting feature
- From: Tom Tromey <tromey at redhat dot com>
- To: Marcelo Taube <mail dot marcelo dot taube at gmail dot com>
- Cc: gdb at sourceware dot org
- Date: Tue, 10 Nov 2009 08:06:05 -0700
- Subject: Re: Some feedback about the python scripting feature
- References: <4AF898F3.50908@gmail.com> <4AF8993D.2050507@gmail.com>
- Reply-to: tromey at redhat dot com
>>>>> "Marcelo" == Marcelo Taube <mail.marcelo.taube@gmail.com> writes:
Marcelo> There are some features missing which would improve it even
Marcelo> more, though.
Feel free to file bug reports in GDB bugzilla.
Marcelo> * *interactive python: *the current python command reads lines using
Marcelo> gdb normal input instead of the regular python prompt line, making
Marcelo> some nice features of python unavailable like
Marcelo> completions-proposals (pressing the tab-key to get the name of a
Marcelo> function completed) or auto indentation. Maybe running the regular
Marcelo> python prompt line can be an option.
You should be able to easily enter the Python repl, though offhand I
don't know how.
Marcelo> * *regular members instead of dictionaries: *it would be more
Marcelo> natural to have members of structs be accessed in their natural
Marcelo> way like in c. For example if we have some struct "struct Type {
Marcelo> int a; int b;}" and we have a value object in python called
Marcelo> 'value', Now to access 'value.a' we have to do 'value["a"]' but
Marcelo> that feels preety unnatural, why not just support the syntax
Marcelo> 'value.a' ?
We chose this approach to avoid conflict with Value's own members, like
`type'.
Tom