From: Daniel Jacobowitz <drow@false.org>
To: gdb@sourceware.org
Subject: Re: GDB and scripting languages - which
Date: Sat, 10 Feb 2007 20:33:00 -0000 [thread overview]
Message-ID: <20070210203307.GA27502@nevyn.them.org> (raw)
In-Reply-To: <uy7n68aee.fsf@gnu.org>
On Sat, Feb 10, 2007 at 02:28:09PM +0200, Eli Zaretskii wrote:
> > Date: Sat, 13 Jan 2007 10:31:51 +0200
> > From: Eli Zaretskii <eliz@gnu.org>
> > CC: gdb@sourceware.org
> >
> > I think adding Python would be a useful first step. It could be the
> > last, or we could later consider Guile as well.
>
> On second thought, what about Lua (http://www.lua.org/)? It looks
> like a language designed specifically for extending software packages.
>
> (Sorry for answering after such a long delay.)
Jim wrote:
> Python has more momentum than Guile in almost any way one might
> measure it:
> - number of users who are familiar with it
> - body of large programs written in it
> - number of modules available for reuse
> - number of programs embedding it
> - number of books available for learning it
I found that very persuasive, and it applies to Lua, though not as
strongly - I see a bit more done with Lua than with Guile, but it
doesn't compare to Python. Also, I know Python, and I think a few
others on this list do - I don't know if anyone here knows Lua.
I spent a while reading the LuaVersusPython wiki page on the Lua Users
wiki. I can't say that I found it very persuasive in either direction
for our situation. Getting Python to work at all is likely to be more
trouble, but not much more trouble, and I'm willing to take care of
that myself. And GDB isn't a lightweight program, which is where much
of Lua's advantage seems to be.
Anyway, just my two cents.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2007-02-10 20:33 UTC|newest]
Thread overview: 56+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-08 22:20 Daniel Jacobowitz
2007-01-08 22:39 ` Kip Macy
2007-01-08 22:42 ` Daniel Jacobowitz
2007-01-08 23:03 ` Kip Macy
2007-01-08 22:40 ` Bob Rossi
2007-01-09 20:11 ` Jim Blandy
2007-01-09 20:23 ` Bob Rossi
2007-01-09 21:37 ` Paul Koning
2007-01-09 21:42 ` Daniel Jacobowitz
2007-01-09 21:48 ` Nick Roberts
2007-01-09 21:53 ` Daniel Jacobowitz
2007-01-11 4:31 ` Nick Roberts
2007-01-11 5:06 ` Daniel Jacobowitz
2007-01-13 8:30 ` Eli Zaretskii
2007-01-09 21:55 ` Kip Macy
2007-01-11 14:56 ` Robert Dewar
2007-01-11 15:07 ` Robert Dewar
2007-01-09 20:30 ` Mark Kettenis
2007-01-13 8:32 ` Eli Zaretskii
2007-02-10 12:28 ` Eli Zaretskii
2007-02-10 18:10 ` Pedro Alves
2007-02-10 20:33 ` Daniel Jacobowitz [this message]
2007-02-12 17:47 ` Jim Blandy
2007-02-12 21:36 ` Eli Zaretskii
2007-02-12 21:59 ` Robert Dewar
2007-02-12 22:07 ` Daniel Jacobowitz
2007-02-12 22:07 ` Robert Dewar
2007-02-14 5:57 ` Jim Blandy
2007-02-14 15:42 ` Eli Zaretskii
2007-02-14 16:01 ` Paul Koning
2007-02-14 17:50 ` Eli Zaretskii
2007-02-14 16:06 ` Daniel Jacobowitz
2007-02-14 18:01 ` Eli Zaretskii
2007-02-14 18:45 ` Daniel Jacobowitz
2007-02-14 17:37 ` Robert Dewar
2007-02-14 18:24 ` Eli Zaretskii
2007-02-14 18:29 ` Robert Dewar
2007-02-14 18:33 ` Eli Zaretskii
2007-02-14 18:34 ` Robert Dewar
2007-02-14 20:14 ` Jim Blandy
2007-02-14 20:56 ` Robert Dewar
2007-02-14 21:47 ` Jim Blandy
2007-02-14 21:23 ` Jim Blandy
2007-02-14 21:46 ` Robert Dewar
2007-02-14 20:10 ` Jim Blandy
2007-02-15 1:03 ` Gaius Mulley
2007-02-17 13:53 ` Eli Zaretskii
2007-02-17 14:07 ` Daniel Jacobowitz
2007-02-18 4:11 ` Robert Dewar
2007-02-19 22:17 ` Jim Blandy
2007-01-15 18:29 Kaz Kylheku
2007-01-15 21:20 ` Eli Zaretskii
2007-01-16 0:17 ` Kip Macy
2007-01-17 19:09 ` Jim Blandy
2007-01-16 0:38 Kaz Kylheku
2007-01-17 19:24 ` Jim Blandy
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=20070210203307.GA27502@nevyn.them.org \
--to=drow@false.org \
--cc=gdb@sourceware.org \
/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