From: Philippe Elie <phil.el@wanadoo.fr>
To: "Dr. David Alan Gilbert" <gilbertd@treblig.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: RFC: Representation of large hex values
Date: Sat, 24 Jan 2004 16:58:17 +0000 [thread overview]
Message-ID: <4012A429.7040902@wanadoo.fr> (raw)
In-Reply-To: 20040124151156.GB1029@gallifrey
Dr. David Alan Gilbert wrote:
> (OK, this isn't strictly a kernel thing - but it seems to be a good
> place for peoples thoughts on this, and the kernel would be one
> place to start it off)
>
> The problem: Large (64 bit) hex values are cumbersome - especially
> when they contain strings of 0's in the middle
>
> Suggestion: Print hex value with a seperator every 4 or 8 nybbles
> to aid in counting. After some discussion it seems that _
> is a decent seperator - e.g.
>
> 1000_0000_0000_1234
You'll break people piping output to tools, you must
solve this by running the output to your own filter
which split hexa number.
regards,
Phil
next prev parent reply other threads:[~2004-01-24 15:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-24 15:11 RFC: Representation of large hex values Dr. David Alan Gilbert
2004-01-24 16:24 ` Andreas Schwab
2004-01-24 16:58 ` Philippe Elie [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-01-24 15:55 Joe Korty
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=4012A429.7040902@wanadoo.fr \
--to=phil.el@wanadoo.fr \
--cc=gilbertd@treblig.org \
--cc=linux-kernel@vger.kernel.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