Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Tom Tromey <tromey@redhat.com>
To: dje@google.com (Doug Evans)
Cc: gdb-patches@sourceware.org
Subject: Re: [RFC] Make "directories" a variable
Date: Fri, 09 Oct 2009 17:35:00 -0000	[thread overview]
Message-ID: <m3skdscvxu.fsf@fleche.redhat.com> (raw)
In-Reply-To: <20091006021038.70688843AC@ruffy.mtv.corp.google.com> (Doug 	Evans's message of "Mon, 5 Oct 2009 19:10:38 -0700 (PDT)")

>>>>> "Doug" == Doug Evans <dje@google.com> writes:

Doug> I like the addition of "set directories mumble", but that's just me,
Doug> and I know better than to be wedded to it. :-)

This part is totally fine by me.  I can't imagine ever actually using
it -- but that is true for any number of already existing parameters :)

Doug> Tom suggested in IRC returning a list in python.
Doug> I don't have a strong opinion on that either,
Doug> it's trivial for the user to work with either form.

There are three reasons I think a python list is better.

1. It conforms more nicely to Python programmer expectations and is
   simply a better API.  This really is a list.
2. Most uses of this parameter will want to use the list form, not the
   string form.
3. If it is a string, then most users will have to write Python code to
   unpack and interpret it.  This is bad because some list elements
   require special treatment, the string is formatted differently on
   different hosts, etc.

Tom


      parent reply	other threads:[~2009-10-09 17:35 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-06  2:11 Doug Evans
2009-10-06  7:18 ` Eli Zaretskii
2009-10-06 18:13 ` Doug Evans
2009-10-09 17:35 ` Tom Tromey [this message]

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=m3skdscvxu.fsf@fleche.redhat.com \
    --to=tromey@redhat.com \
    --cc=dje@google.com \
    --cc=gdb-patches@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