From: Doug Evans <xdje42@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: ludo@gnu.org (Ludovic Courtès), gdb-patches@sourceware.org
Subject: Re: [PATCH v1 02/36] Guile extension language: doc additions
Date: Thu, 16 Jan 2014 04:20:00 -0000 [thread overview]
Message-ID: <m3lhygo8vu.fsf@sspiff.org> (raw)
In-Reply-To: <83r48nv7op.fsf@gnu.org> (Eli Zaretskii's message of "Sat, 04 Jan 2014 22:00:22 +0200")
Eli Zaretskii <eliz@gnu.org> writes:
>> From: ludo@gnu.org (Ludovic Courtès)
>> Cc: gdb-patches@sourceware.org
>> Date: Sat, 04 Jan 2014 18:42:44 +0100
>>
>> > Well, GDB supports long double if the target does, so I thought it
>> > would be a pity to lose that when working with Guile.
>>
>> We’re talking about ‘make-value’ here, which does allow users to create
>> a ‘long double’ value, AIUI.
>>
>> What’s lost is that users can only inject in the debuggee values with
>> the accuracy of a ‘double’.
>>
>> This is a theoretical limitation, but I’m tempted to think that this is
>> rarely (if ever) a concern in practice.
>>
>> How do the Python bindings handle this?
>
> I don't know. Maybe someone else could chime in.
The python code in gdb just uses doubles.
There's nothing precluding supporting better precision in the future,
but for this pass I'd like to keep it simple.
next prev parent reply other threads:[~2014-01-16 4:20 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-24 19:03 Doug Evans
2013-12-25 19:27 ` Eli Zaretskii
2014-01-03 21:31 ` Ludovic Courtès
2014-01-04 7:12 ` Eli Zaretskii
2014-01-04 11:57 ` Ludovic Courtès
2014-01-04 14:41 ` Eli Zaretskii
2014-01-04 17:42 ` Ludovic Courtès
2014-01-04 20:00 ` Eli Zaretskii
2014-01-16 4:20 ` Doug Evans [this message]
2014-01-18 20:36 ` Doug Evans
2014-01-18 20:52 ` Ludovic Courtès
2014-01-18 20:55 ` Doug Evans
2014-01-19 16:58 ` Eli Zaretskii
2014-01-19 17:19 ` Doug Evans
2014-01-19 17:34 ` Eli Zaretskii
2014-01-19 17:53 ` Doug Evans
2014-01-19 18:10 ` Eli Zaretskii
2014-01-19 21:19 ` Doug Evans
2014-01-18 20:16 ` Doug Evans
2014-01-18 20:42 ` Ludovic Courtès
2014-01-18 21:57 ` Doug Evans
2014-01-19 14:46 ` Ludovic Courtès
2014-01-19 21:37 ` Doug Evans
2014-01-19 22:50 ` Ludovic Courtès
2014-01-18 22:32 ` Doug Evans
2014-01-19 14:47 ` Ludovic Courtès
2014-01-19 15:56 ` Eli Zaretskii
2014-01-19 16:13 ` Ludovic Courtès
2014-01-19 17:05 ` Doug Evans
2014-01-18 20:06 ` Doug Evans
2014-01-18 20:24 ` Eli Zaretskii
2014-01-18 20:53 ` Doug Evans
2014-01-19 16:57 ` Eli Zaretskii
2014-01-19 17:42 ` Doug Evans
2014-01-19 21:01 ` Doug Evans
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=m3lhygo8vu.fsf@sspiff.org \
--to=xdje42@gmail.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=ludo@gnu.org \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).