Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Phil Muldoon <pmuldoon@redhat.com>
To: Siva Chandra <sivachandra@google.com>
Cc: Doug Evans <dje@google.com>, gdb-patches@sourceware.org
Subject: Re: [RFC] A new command 'explore'
Date: Fri, 17 Feb 2012 13:14:00 -0000	[thread overview]
Message-ID: <4F3E41F7.2000006@redhat.com> (raw)
In-Reply-To: <CAGyQ6gxND0v4QCHuZ9Dc0H0QpWBfPJvkTX15JYX-o9K5Um4KuQ@mail.gmail.com>

On 02/17/2012 09:55 AM, Siva Chandra wrote:
> Doug > I'm not sure what others prefer, but I like the python

> Along with the fact that there wasn't anything available
> on the policy for contributions in extensions languages, I have seen
> that GUILE is now going to be another officially supported extension
> language. In which case, if 'explore' can be useful to a wide
> audience, isn't it better in C so that it is available to everyone?

You can of course choose to submit the patch however you wish ... you
are the author!  But I do not think the discussions on GUILE should
preclude any continuing effort on commands written in Python.  Not a
single API exists for GUILE at the moment. So my 2 cents, I agree with
Doug, I liked the Python version better.

Cheers,

Phil



  reply	other threads:[~2012-02-17 12:03 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAGyQ6gyAwr2zuv3NYpdk09vPyYpuFkyiErEhw-vws-WfuLDxiw@mail.gmail.com>
2011-12-19 19:05 ` Siva Chandra
2011-12-21 19:36   ` Tom Tromey
2011-12-22 11:00     ` Siva Chandra
2011-12-22  5:21   ` Joel Brobecker
2011-12-22 11:48     ` Siva Chandra
2011-12-22 12:53       ` Joel Brobecker
2011-12-27  6:29   ` Siva Chandra
2012-02-08  9:34     ` Siva Chandra
2012-02-17  7:40       ` Doug Evans
2012-02-17 10:00         ` Siva Chandra
2012-02-17 13:14           ` Phil Muldoon [this message]
2012-02-17 10:09         ` Siva Chandra

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=4F3E41F7.2000006@redhat.com \
    --to=pmuldoon@redhat.com \
    --cc=dje@google.com \
    --cc=gdb-patches@sourceware.org \
    --cc=sivachandra@google.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