From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 59167 invoked by alias); 17 Mar 2015 22:21:42 -0000 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 Received: (qmail 59158 invoked by uid 89); 17 Mar 2015 22:21:41 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-2.6 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_LOW,SPF_PASS,T_RP_MATCHES_RCVD autolearn=ham version=3.3.2 X-HELO: mail-ob0-f176.google.com Received: from mail-ob0-f176.google.com (HELO mail-ob0-f176.google.com) (209.85.214.176) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (AES128-GCM-SHA256 encrypted) ESMTPS; Tue, 17 Mar 2015 22:21:39 +0000 Received: by obdfc2 with SMTP id fc2so18889706obd.3 for ; Tue, 17 Mar 2015 15:21:38 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=ikuan9bKc2LFrARwVtvwsK9jPEjIDmRXO8lMKV260Og=; b=lrN9o7OpdFG45TLbHz+xMELV+jinTWvHHWBECzKzut596MwYeVOvZyPZO4b5f3GnB6 Erbj1fIxU61ypLMysrwVkePNUqUPBr/XbtIN/ukeGJKo5vwggodAJogTt/m1Fbwjy4aT 4n7xXeAFgcjxyRffqmNZC/gy5bSbf7NmXOy/KLKTyCWhNxcGeFhNNA9oS9l4XT/hWWQd glyMxIKrXgPfsiHYQ9RqOV+IbY1l47H0OP6SVwU3B5S8ckkrdKmMzcCZIsvokOLOISlM h4Nw/aduVBC/bfYhrldfnfdmMVgNEFzJh97NdQYS3J/Kpy2FAJer5cTCdz7kZbCFATKp 63tQ== X-Gm-Message-State: ALoCoQkUw1BmXymFYm3enND7HwMm4IzdMiWNROzWGe/x+4JrQ8oDNpcVvZK1y7EcR2hS1m0zjfhr MIME-Version: 1.0 X-Received: by 10.60.47.42 with SMTP id a10mr55043577oen.75.1426630898053; Tue, 17 Mar 2015 15:21:38 -0700 (PDT) Received: by 10.182.142.226 with HTTP; Tue, 17 Mar 2015 15:21:37 -0700 (PDT) In-Reply-To: <87sid4atms.fsf@igalia.com> References: <21714.40641.510825.30998@ruffy2.mtv.corp.google.com> <54E71694.1080304@redhat.com> <87ioei31uj.fsf@igalia.com> <87d24p19tt.fsf@igalia.com> <54FD7DAA.7010603@redhat.com> <87twxrncld.fsf@igalia.com> <87ioe1dvu2.fsf@igalia.com> <87sid4atms.fsf@igalia.com> Date: Tue, 17 Mar 2015 22:21:00 -0000 Message-ID: Subject: Re: [RFC] [PATCH] Provide the ability to write the frame unwinder in Python From: Doug Evans To: Andy Wingo Cc: Alexander Smundak , gdb-patches , guile-devel@gnu.org Content-Type: text/plain; charset=UTF-8 X-IsSubscribed: yes X-SW-Source: 2015-03/txt/msg00528.txt.bz2 [+ guile-devel, in case they have an opinion on the spelling of frame-data-read-register vs frame-data:read-register] On Tue, Mar 17, 2015 at 1:57 AM, Andy Wingo wrote: >> As to the class of an object passed to a sniffer, how about calling it >> FrameData? Note that it's not very important from the user's point of >> view as sniffer code does not ever reference it by name. > > It's true that from user code it barely matters to Python, but Scheme's > monomorphic flavor makes these things more apparent: > > (frame-data-read-register frame "r0") > > This doesn't read so well to me -- is it "read-register" on a > "frame-data", or is it "data-read-register" on a "frame" ? A weak point > but "ephemeral-frame-read-register" avoids the question. As food for discussion, I know some people use foo:bar in Scheme to separate the object "foo" from the operation on it "bar". -> frame-data:read-register I like having some separator, but I went with what I thought was the preferred spelling (all -'s). It's not too late to change gdb/guile to use foo:bar throughout (IMO), but the door is closing.