unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Andy Wingo <wingo@pobox.com>
To: Tom Tromey <tromey@redhat.com>
Cc: guile-devel@gnu.org
Subject: Re: guile support in gdb
Date: Fri, 08 Oct 2010 10:19:41 +0200	[thread overview]
Message-ID: <m3wrptf65e.fsf@unquote.localdomain> (raw)
In-Reply-To: <m3y6a9v5aw.fsf@fleche.redhat.com> (Tom Tromey's message of "Thu, 07 Oct 2010 19:31:19 -0600")

On Fri 08 Oct 2010 03:31, Tom Tromey <tromey@redhat.com> writes:

>>>>>> "Andy" == Andy Wingo <wingo@pobox.com> writes:
>
> Andy> That's unfortunate. Guile is the GNU extension language, you know.
>
> Yeah, I know.
>
> While the decision to use Python was made before I was active in GDB
> (look in the archives around Jan 2007 for the thread), and while I am
> actually not a fan of Python, I do basically agree with this choice.  My
> reason is that I think it is important to have a popular language with a
> wide variety of available libraries.  Python is a very easy sell to
> various GDB user communities.

Yeah, understood. Guile wasn't doing all that well either in 2007, so it
wasn't quite the obvious choice, and still has a ways to go before
popularity strikes; but otoh it does allow for other languages,
including javascript. Not that that support is really where I want it to
be yet..

Anyway, perhaps we will revisit this conversation in a couple years.

Happy hacking,

Andy
-- 
http://wingolog.org/



  reply	other threads:[~2010-10-08  8:19 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-07 18:39 guile support in gdb Tom Tromey
2010-10-07 20:10 ` Andy Wingo
2010-10-07 21:27   ` Tom Tromey
2010-10-07 22:14     ` Andy Wingo
2010-10-08  1:31       ` Tom Tromey
2010-10-08  8:19         ` Andy Wingo [this message]
2010-10-07 21:35 ` Ludovic Courtès

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

  List information: https://www.gnu.org/software/guile/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=m3wrptf65e.fsf@unquote.localdomain \
    --to=wingo@pobox.com \
    --cc=guile-devel@gnu.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).