[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [RFC] [PATCH] Provide the ability to write the frame unwinder in Pyt

From: Doug Evans
Subject: Re: [RFC] [PATCH] Provide the ability to write the frame unwinder in Python
Date: Tue, 17 Mar 2015 15:21:37 -0700

[+ 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 <address@hidden> 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.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]