From: Jan Blunck <jblunck@suse.de>
To: Tom Tromey <tromey@redhat.com>
Cc: Frysk List <frysk@sourceware.org>
Subject: Re: Changes
Date: Thu, 17 Jul 2008 07:51:00 -0000 [thread overview]
Message-ID: <20080717075059.GL10069@bolzano.suse.de> (raw)
In-Reply-To: <m33ami66rk.fsf@fleche.redhat.com>
On Wed, Jul 09, Tom Tromey wrote:
> * Scripting. One issue with gdb is its poor support for scripting.
> We think scripting is needed for debugger programmability, and in
> particular that it will be needed for C++ pretty-printing. So, our
> thinking is that this debugger would have a Python binding to its
> core.
>
> In order to exercise this binding code, we picture rewriting the
> existing CLI code in Python. The idea here is that part of the CLI
> need a rewrite anyhow, and there is no particular reason that the
> CLI needs to be written in C++.
I find it somehow unnatural that the scripting capabilities are based on
python while the target language is C/C++.
From my point of view it would make sense to use a language similar to C, e.g.
like SIAL. Or at least provide the scripting capabilities as plugins.
Cheers,
Jan
prev parent reply other threads:[~2008-07-17 7:51 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-09 22:19 Changes Tom Tromey
2008-07-10 0:06 ` Changes Sami Wagiaalla
2008-07-11 17:04 ` Changes Sami Wagiaalla
2008-07-10 4:17 ` Changes Thiago Jung Bauermann
2008-07-10 5:43 ` Changes Sami Wagiaalla
2008-07-10 13:14 ` Changes Rick Moseley
2008-07-10 13:26 ` Changes Phil Muldoon
2008-07-10 17:07 ` Changes Eric Bachalo
2008-07-10 19:43 ` Changes Dodji Seketeli
2008-07-11 16:55 ` Changes Tom Tromey
2008-07-10 8:24 ` Changes Phil Muldoon
2008-07-11 10:44 ` Changes Phil Muldoon
2008-07-17 7:51 ` Jan Blunck [this message]
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=20080717075059.GL10069@bolzano.suse.de \
--to=jblunck@suse.de \
--cc=frysk@sourceware.org \
--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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).