From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 23439 invoked by alias); 16 Aug 2011 10:48:14 -0000 Received: (qmail 23430 invoked by uid 22791); 16 Aug 2011 10:48:13 -0000 X-SWARE-Spam-Status: No, hits=-2.3 required=5.0 tests=AWL,BAYES_00,RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org Received: from ausxippc101.us.dell.com (HELO ausxippc101.us.dell.com) (143.166.85.207) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Tue, 16 Aug 2011 10:48:00 +0000 X-Loopcount0: from 10.170.28.40 From: To: CC: , Date: Tue, 16 Aug 2011 10:48:00 -0000 Subject: RE: [Python] Allow attribute references to gdb.Value objects Message-ID: <09787EF419216C41A903FD14EE5506DD0151D5839E@AUSX7MCPC103.AMER.DELL.COM> References: <3A56CC74-0A48-47E8-BBA2-6E2BEB2FB588@comcast.net> <09787EF419216C41A903FD14EE5506DD0151D58146@AUSX7MCPC103.AMER.DELL.COM> <09787EF419216C41A903FD14EE5506DD0151D581B5@AUSX7MCPC103.AMER.DELL.COM> In-Reply-To: Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-IsSubscribed: yes Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org X-SW-Source: 2011-08/txt/msg00324.txt.bz2 > 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 t= hem 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 e= nd in breakage. Ok, I guess I'll drop the idea, and rewrite my own scripts accordingly. paul