From: Tom Tromey <tromey@redhat.com>
To: Paul Koning <Paul_Koning@Dell.com>
Cc: jimb@red-bean.com, bauerman@br.ibm.com, gdb@sourceware.org
Subject: Re: repo to work on python scripting support
Date: Wed, 26 Mar 2008 03:23:00 -0000 [thread overview]
Message-ID: <m37ifqmtni.fsf@fleche.redhat.com> (raw)
In-Reply-To: <18409.21257.48822.645806@pkoning-laptop.equallogic.com> (Paul Koning's message of "Tue\, 25 Mar 2008 15\:31\:21 -0400")
>>>>> "Paul" == Paul Koning <Paul_Koning@Dell.com> writes:
Paul> Something akin to the way that C extension modules inside Python tell
Paul> the Python execution machinery what data type it wants might serve.
Yeah.
Paul> The notion of asking for a particular type is a bit foreign to Python;
Paul> arguments have no fixed type.
"Type" here was a confusing choice of word. It is really just about
having a declarative way to decide how to parse the argument string.
Paul> Another possibility is to pass strings but then have standard
Paul> conversion routines (things callable by Python and supplied by gdb).
Paul> For example parse_and_eval_address. And the target functions. And so
Paul> on.
One nice property of the declarative approach is that the core code
can automatically handle completion as well as parsing.
One idea is to let a Python class define a special method which is
used to parse the string. If there is no such method, we would look
for declarative properties.
Tom
next prev parent reply other threads:[~2008-03-25 21:28 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 [this message]
2008-03-26 12:55 ` Jim Blandy
2008-03-26 17:29 ` Paul Koning
2008-03-26 17:58 ` Daniel Jacobowitz
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=m37ifqmtni.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=Paul_Koning@Dell.com \
--cc=bauerman@br.ibm.com \
--cc=gdb@sourceware.org \
--cc=jimb@red-bean.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