From: "Eli Zaretskii" <eliz@elta.co.il>
To: Daniel Jacobowitz <drow@mvista.com>
Cc: cagney@gnu.org, gdb-patches@sources.redhat.com
Subject: Re: [RFC]: remove inconsistency in printcmd.c: print_scalar_formatted
Date: Tue, 20 Jan 2004 20:32:00 -0000 [thread overview]
Message-ID: <1659-Tue20Jan2004222747+0200-eliz@elta.co.il> (raw)
In-Reply-To: <20040120193349.GA26311@nevyn.them.org> (message from Daniel Jacobowitz on Tue, 20 Jan 2004 14:33:49 -0500)
> Date: Tue, 20 Jan 2004 14:33:49 -0500
> From: Daniel Jacobowitz <drow@mvista.com>
>
> I'll respond to these all together, since there's really the same
> answer to all of them: I think there is a general unimplemented feature
> here, not just the specific "show me the hex representation of this
> double". Examples I have in mind:
> - Displaying an integer to a sequence of characters
> p/s 0x6263 -> "ab"
> - Displaying a double-precision value in hex:
> p/x 2.0 -> 0x4000000000000000
> - Displaying a double-precision value in binary:
> p/t 2.0 -> 01000000000000000000000000000000
> 00000000000000000000000000000000
> - Displaying an integer (hex or otherwise) value as a double
> p/f 0x4000000000000000LL -> 2.0
> - Displaying an integer (hex or otherwise) value as a long
> double - this one is trickier, since we don't normally have an
> integer type that is big enough, but if we did:
> p/gf 0x400000000000000000000000LLL -> 2.0
Sounds like there's a place for a new command, since what we want here
is a command that would interpret a value as some different type. Do
you agree?
next prev parent reply other threads:[~2004-01-20 20:32 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-12 20:36 Jeff Johnston
2003-12-12 22:17 ` Kevin Buettner
2003-12-12 23:05 ` Daniel Jacobowitz
2003-12-13 0:55 ` J. Johnston
2004-01-19 22:23 ` J. Johnston
2004-01-19 22:57 ` Andrew Cagney
2004-01-19 23:18 ` Daniel Jacobowitz
2004-01-19 23:27 ` Kevin Buettner
2004-01-20 0:41 ` Andrew Cagney
2004-01-20 1:22 ` Daniel Jacobowitz
[not found] ` <400C8CC0.3040706@gnu.org>
2004-01-20 5:48 ` Daniel Jacobowitz
2004-01-20 6:55 ` Eli Zaretskii
2004-01-20 14:52 ` Daniel Jacobowitz
2004-01-20 19:15 ` Eli Zaretskii
2004-01-20 19:33 ` Daniel Jacobowitz
2004-01-20 20:32 ` Eli Zaretskii [this message]
2004-01-20 16:50 ` Andrew Cagney
2004-01-20 19:10 ` Eli Zaretskii
2004-01-20 21:29 ` Andrew Cagney
2004-02-19 22:53 ` Jeff Johnston
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=1659-Tue20Jan2004222747+0200-eliz@elta.co.il \
--to=eliz@elta.co.il \
--cc=cagney@gnu.org \
--cc=drow@mvista.com \
--cc=gdb-patches@sources.redhat.com \
/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