From: Eli Zaretskii <eliz@gnu.org>
To: Daniel Jacobowitz <drow@false.org>
Cc: steverod@netapp.com, gdb-patches@sources.redhat.com
Subject: Re: [patch] Indirect access to GDB history variables
Date: Sat, 16 Dec 2006 19:43:00 -0000 [thread overview]
Message-ID: <uwt4rtyml.fsf@gnu.org> (raw)
In-Reply-To: <20061216184508.GA17120@nevyn.them.org> (message from Daniel Jacobowitz on Sat, 16 Dec 2006 13:45:08 -0500)
> Date: Sat, 16 Dec 2006 13:45:08 -0500
> From: Daniel Jacobowitz <drow@false.org>
> Cc: steverod@netapp.com, gdb-patches@sources.redhat.com
>
> > if the embedded language will satisfy Steve's needs, I'm for it. But
> > I fear that agreeing on the language will take time, in which case
> > postponing this change will be just that.
>
> It may be so. My tentative plan was to offer a selection, probably
> Perl and Python and Guile; once the common infrastructure is in place,
> it's really not hard to add languages and enable them at configure
> time. The alternative would be to add only Guile, since that's the
> language the FSF officially recommends for such things - I don't want
> to take that alternative, though, since I'm practically useless in
> Guile. I have implemented Guile embedding, by the way, though never
> finished it up.
I have no objections for the list of languages you suggested.
We could also just accept Steve's patch and see if anyone hollers.
The next release is still far away, so we have enough to time to see
if something breaks as the result.
next prev parent reply other threads:[~2006-12-16 19:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-15 2:41 Steve Rodrigues
2006-12-15 8:43 ` Eli Zaretskii
2006-12-16 17:10 ` Daniel Jacobowitz
2006-12-16 18:40 ` Eli Zaretskii
2006-12-16 18:45 ` Daniel Jacobowitz
2006-12-16 19:43 ` Eli Zaretskii [this message]
2006-12-18 5:46 ` Steve Rodrigues
2006-12-18 13:40 ` Daniel Jacobowitz
[not found] <20061215182551.GA10789@siml11.eng.netapp.com>
2006-12-16 9:34 ` Eli Zaretskii
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=uwt4rtyml.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=drow@false.org \
--cc=gdb-patches@sources.redhat.com \
--cc=steverod@netapp.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