From: Daniel Jacobowitz <drow@false.org>
To: Paul Koning <Paul_Koning@dell.com>
Cc: jimb@red-bean.com, tromey@redhat.com, bauerman@br.ibm.com,
gdb@sourceware.org
Subject: Re: repo to work on python scripting support
Date: Wed, 26 Mar 2008 17:58:00 -0000 [thread overview]
Message-ID: <20080326142402.GA15660@caradoc.them.org> (raw)
In-Reply-To: <18410.23162.503583.519896@gargle.gargle.HOWL>
On Wed, Mar 26, 2008 at 10:15:22AM -0400, Paul Koning wrote:
> The goal of supporting Python scripting should be to provide an
> environment that is familiar to Python programmers.
No, I don't think so. The goal of supporting Python scripting is
to make it easy to implement useful and usable GDB commands in a
way accessible to Python programmers.
These are functions which will be directly shown to the user. We
need _consistency_ in how their arguments are passed; experience has
shown that inconsistency is a serious problem. I don't think any
sort of polymorphism is going to be necessary or desirable in
practice.
Don't confuse this with typing. It's just going to say EXPRESSION
and if you want to handle strings and ints, that's fine. The "caller"
is the human user typing some characters.
Can you give me an example of where it would be more useful not to
do it this way? Regardless of the details of how we pre-specify
arguments.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2008-03-26 14:24 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-16 0:42 Thiago Jung Bauermann
2008-03-16 2:55 ` Tom Tromey
2008-03-24 17:16 ` Thiago Jung Bauermann
2008-03-25 11:45 ` Tom Tromey
2008-03-25 13:53 ` Daniel Jacobowitz
2008-03-25 18:37 ` Jim Blandy
2008-03-25 18:52 ` Daniel Jacobowitz
2008-03-25 18:53 ` Jim Blandy
2008-03-25 19:18 ` Tom Tromey
2008-03-27 6:41 ` Jim Blandy
2008-03-27 17:57 ` Paul Koning
2008-03-25 19:31 ` Paul Koning
2008-03-25 20:18 ` Tom Tromey
2008-03-25 20:31 ` Paul Koning
2008-03-26 3:23 ` Tom Tromey
2008-03-26 12:55 ` Jim Blandy
2008-03-26 17:29 ` Paul Koning
2008-03-26 17:58 ` Daniel Jacobowitz [this message]
2008-03-26 18:41 ` Tom Tromey
2008-03-26 20:04 ` Paul Koning
2008-03-26 22:45 ` Jim Blandy
2008-03-26 18:05 ` Doug Evans
2008-03-26 18:13 ` Daniel Jacobowitz
2008-03-26 18:25 ` Tom Tromey
2008-03-26 18:41 ` Daniel Jacobowitz
2008-03-26 18:55 ` Tom Tromey
2008-03-26 20:57 ` Daniel Jacobowitz
2008-03-26 21:01 ` Thiago Jung Bauermann
2008-03-27 14:11 ` Jim Blandy
2008-03-27 16:49 ` Paul Koning
2008-03-26 18:23 ` Tom Tromey
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=20080326142402.GA15660@caradoc.them.org \
--to=drow@false.org \
--cc=Paul_Koning@dell.com \
--cc=bauerman@br.ibm.com \
--cc=gdb@sourceware.org \
--cc=jimb@red-bean.com \
--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