From: "H. Peter Anvin" <hpa@zytor.com>
To: linux-kernel@vger.kernel.org
Subject: Re: Octal vs. Hex war o' death
Date: 29 Nov 2000 16:22:31 -0800 [thread overview]
Message-ID: <9046k7$nrf$1@cesium.transmeta.com> (raw)
In-Reply-To: <3A2590C8.34459BF9@echostar.com> <20001129181723.A2765@potty.housenet>
Followup to: <20001129181723.A2765@potty.housenet>
By author: Jeff Epler <jepler@inetnebr.com>
In newsgroup: linux.dev.kernel
>
> On Wed, Nov 29, 2000 at 04:27:04PM -0700, Ian S. Nelson wrote:
> > c) octals were invented for UNIX file permissions and not
> > programming
>
> You must be joking. Read much history of computing? Or
> alt.folklore.computers? Octal was very natural for 18- and 36-bit
> machines, after all.
>
Not to mention that it's still quite natural for a lot of machines.
If you ever look at raw x86 machine code, with it's 3-bit fields,
byteized octal actually makes it quite easy to read.
Octal probably predates hexadecimal, since it fit within the 0-9
digits most people used. Hex is really the natural choice for
modern power-of-two-width machines, though.
-hpa
--
<hpa@transmeta.com> at work, <hpa@zytor.com> in private!
"Unix gives you enough rope to shoot yourself in the foot."
http://www.zytor.com/~hpa/puzzle.txt
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2000-11-30 0:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-29 23:27 Octal vs. Hex war o' death Ian S. Nelson
2000-11-30 0:17 ` Jeff Epler
2000-11-30 0:22 ` H. Peter Anvin [this message]
2000-11-30 0:39 ` PROBLEM: do_try_free_pages failed for python Bob Tanner
2000-11-30 16:06 ` Rik van Riel
2000-11-30 16:29 ` Andrea Arcangeli
2000-11-30 0:43 ` Octal vs. Hex war o' death Alexander Viro
2000-11-30 4:07 ` Igmar Palsenberg
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='9046k7$nrf$1@cesium.transmeta.com' \
--to=hpa@zytor.com \
--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 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.