Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Tom Tromey <tromey@redhat.com>
To: Marcelo Taube <mail.marcelo.taube@gmail.com>
Cc: gdb@sourceware.org
Subject: Re: Some feedback about the python scripting feature
Date: Tue, 10 Nov 2009 15:38:00 -0000	[thread overview]
Message-ID: <m34op2e7xe.fsf@fleche.redhat.com> (raw)
In-Reply-To: <4AF8993D.2050507@gmail.com> (Marcelo Taube's message of "Tue, 10 	Nov 2009 00:35:41 +0200")

>>>>> "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


  parent reply	other threads:[~2009-11-10 15:06 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <4AF898F3.50908@gmail.com>
2009-11-10  8:06 ` Marcelo Taube
2009-11-10 15:12   ` Phil Muldoon
2009-11-10 15:38   ` Tom Tromey [this message]
2009-11-10 16:53     ` Daniel Jacobowitz
2009-11-10 20:49       ` Marcelo Taube
2009-11-11  2:00         ` Daniel Jacobowitz
2009-11-13 21:37       ` scott snyder

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=m34op2e7xe.fsf@fleche.redhat.com \
    --to=tromey@redhat.com \
    --cc=gdb@sourceware.org \
    --cc=mail.marcelo.taube@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