From: Segher Boessenkool <segher@kernel.crashing.org>
To: Dan Malek <dan@embeddedalley.com>
Cc: linuxppc-dev list <linuxppc-dev@ozlabs.org>, Jon Loeliger <jdl@jdl.com>
Subject: Re: [DTC PATCH] Add support for decimal, octal and binary based cell values.
Date: Fri, 16 Feb 2007 11:21:19 +0100 [thread overview]
Message-ID: <a11c8a770fa2fd412330b9d89d8ebe5f@kernel.crashing.org> (raw)
In-Reply-To: <70840B5D-F927-4CC6-84D3-789DA8A66378@embeddedalley.com>
> Why do we need yet another syntax? Everyone
> else, including most silicon documentation, uses
> the standard "C" syntax 0x for hex, 0 for octal, and
> nothing for decimal.
[Completely off-topic]
You're joking, right? Many docs use 1234h for hex and
1011b for binary; or $1234 for hex and %1011 for binary;
or x'1234 and b'1011; or 1234_{(16)} and 1011_{(2)} (TeX
notation -- base as decimal in a parenthesised subscript);
etc. etc. etc.
Almost all computer languages use something more sane
than the C-family stuff too (esp. the dreaded "0 is
octal" thing is not exactly great).
Anyway, really off-topic :-)
Segher
prev parent reply other threads:[~2007-02-16 10:21 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-15 17:13 [DTC PATCH] Add support for decimal, octal and binary based cell values Jon Loeliger
2007-02-15 17:30 ` Kumar Gala
2007-02-15 17:49 ` Yoder Stuart-B08248
2007-02-15 18:41 ` Kumar Gala
2007-02-15 22:14 ` David Gibson
2007-02-16 0:04 ` Kumar Gala
2007-02-16 10:23 ` Segher Boessenkool
2007-02-15 17:45 ` Yoder Stuart-B08248
2007-02-15 18:00 ` Olof Johansson
2007-02-15 18:00 ` Yoder Stuart-B08248
2007-02-15 18:02 ` Scott Wood
2007-02-15 18:05 ` Jon Loeliger
2007-02-15 18:10 ` Yoder Stuart-B08248
2007-02-15 21:44 ` Benjamin Herrenschmidt
2007-02-15 22:12 ` David Gibson
2007-02-15 22:59 ` Jon Loeliger
2007-02-15 22:19 ` David Gibson
2007-02-15 23:43 ` Jon Loeliger
2007-02-15 22:33 ` Dan Malek
2007-02-15 22:57 ` David Gibson
2007-02-15 23:37 ` Dan Malek
2007-02-16 0:09 ` David Gibson
2007-02-16 10:21 ` Segher Boessenkool [this message]
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=a11c8a770fa2fd412330b9d89d8ebe5f@kernel.crashing.org \
--to=segher@kernel.crashing.org \
--cc=dan@embeddedalley.com \
--cc=jdl@jdl.com \
--cc=linuxppc-dev@ozlabs.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.