public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: "Mark Kettenis" <mark.kettenis@xs4all.nl>
To: "Joel Brobecker" <brobecker@adacore.com>
Cc: "Mike Frysinger" <vapier@gentoo.org>, gdb-patches@sourceware.org
Subject: Re: GDB and Guile
Date: Wed, 11 Jan 2012 09:48:00 -0000	[thread overview]
Message-ID: <0ea813fb91e432223fffab25cc01b9c7.squirrel@webmail.xs4all.nl> (raw)
In-Reply-To: <20120111030958.GD31383@adacore.com>

> > i know the request/announce doesn't say it would, but i hope that
> > gaining Guile support wouldn't affect existing python support
>
>  I can confirm that Python support will not be affected.

But I'd say that, given the limited resources we have, supporting two
extension languages is undesirable.  Let's face it, Guile support is
something
that Stallman wants, but probably not a lot of other people.  Now if somebody
steps up to do the work and is motivated enough to build a community to
support it (like what happened with Python support) we should of course
seriously consider integrating that work.  But if somebody wants to do
this just because Stallman says so, I think we shouldn't encourage
him/her.


  reply	other threads:[~2012-01-11  9:06 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20120109032350.GJ2716@adacore.com>
2012-01-09  4:33 ` Andrey Smirnov
2012-01-09 16:24   ` Tom Tromey
     [not found]   ` <CA+jSXqa_SgOaNscr48FPiab5Tt+p2dJoD1A6B2Qbzbf3uXJs0g@mail.gmail.com>
2012-01-10  4:32     ` Joel Brobecker
2012-01-11  0:18       ` Jiang Jilin
2012-01-11  3:10 ` Mike Frysinger
2012-01-11  3:25   ` Joel Brobecker
2012-01-11  9:48     ` Mark Kettenis [this message]
2012-06-28 15:09 Tom Emerson
2012-06-28 19:41 ` Doug Evans
2012-07-09 16:20 ` Ludovic Courtès
2012-07-09 20:35   ` Tom Emerson
2012-07-09 21:10     ` Tom Tromey
2012-07-10 13:30       ` Tom Emerson

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=0ea813fb91e432223fffab25cc01b9c7.squirrel@webmail.xs4all.nl \
    --to=mark.kettenis@xs4all.nl \
    --cc=brobecker@adacore.com \
    --cc=gdb-patches@sourceware.org \
    --cc=vapier@gentoo.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).