Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: <Paul_Koning@Dell.com>
To: <drow@false.org>
Cc: <tromey@redhat.com>, <gdb-patches@sourceware.org>
Subject: RE: [Python] Allow attribute references to gdb.Value objects
Date: Tue, 16 Aug 2011 10:48:00 -0000	[thread overview]
Message-ID: <09787EF419216C41A903FD14EE5506DD0151D5839E@AUSX7MCPC103.AMER.DELL.COM> (raw)
In-Reply-To: <CAN9gPaEq+=FGFFh+_eCW5aKPQ-3-k98bDz_FGLwYKoEqWbeCmw@mail.gmail.com>

> IMO, the robustness choice outweighs this consideration.  While a lot of these scripts are for a single-purpose session, I'm finding that we check them in somewhere and adapt them to future bugs.  I'm sure they'll break in all sorts of interesting ways; I'd rather not add one that we *know* will end in breakage.

Ok, I guess I'll drop the idea, and rewrite my own scripts accordingly.

	paul


      reply	other threads:[~2011-08-16 10:48 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-12 19:33 Paul Koning
2011-08-15 19:09 ` Tom Tromey
2011-08-15 20:30   ` Paul_Koning
2011-08-15 20:43     ` Tom Tromey
2011-08-15 20:54       ` Paul_Koning
2011-08-16  1:12         ` Daniel Jacobowitz
2011-08-16 10:48           ` Paul_Koning [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=09787EF419216C41A903FD14EE5506DD0151D5839E@AUSX7MCPC103.AMER.DELL.COM \
    --to=paul_koning@dell.com \
    --cc=drow@false.org \
    --cc=gdb-patches@sourceware.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