This is the mail archive of the gdb-patches@sourceware.org mailing list for the GDB project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

RE: [Python] Allow attribute references to gdb.Value objects

From: <Paul_Koning at Dell dot com>
To: <drow at false dot org>
Cc: <tromey at redhat dot com>, <gdb-patches at sourceware dot org>
Date: Tue, 16 Aug 2011 05:47:58 -0500
Subject: RE: [Python] Allow attribute references to gdb.Value objects
References: <3A56CC74-0A48-47E8-BBA2-6E2BEB2FB588@comcast.net> <m3bovqebki.fsf@fleche.redhat.com> <09787EF419216C41A903FD14EE5506DD0151D58146@AUSX7MCPC103.AMER.DELL.COM> <m3pqk6csop.fsf@fleche.redhat.com> <09787EF419216C41A903FD14EE5506DD0151D581B5@AUSX7MCPC103.AMER.DELL.COM> <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

References:
- [Python] Allow attribute references to gdb.Value objects
  - From: Paul Koning
- Re: [Python] Allow attribute references to gdb.Value objects
  - From: Tom Tromey
- RE: [Python] Allow attribute references to gdb.Value objects
  - From: Paul_Koning
- Re: [Python] Allow attribute references to gdb.Value objects
  - From: Tom Tromey
- RE: [Python] Allow attribute references to gdb.Value objects
  - From: Paul_Koning
- Re: [Python] Allow attribute references to gdb.Value objects
  - From: Daniel Jacobowitz

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]