From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] simplicity
Date: Wed, 19 Sep 2007 07:51:48 -0400 [thread overview]
Message-ID: <c1ee80d3c2b50c2b12d22a11d7d703dc@quanstro.net> (raw)
In-Reply-To: <46F02B21.69FA68B2@null.net>
> So what is supposed to be wrong with using a manifest constant
> instead of hard-coding "8" in various places? As I recall,
> The Elements of Programming Style recommended this approach.
i see two problems with this sort of indirection. if i see NBBY
in the code, i have to look up it's value. NBBY doesn't mean anything
to me. this layer of mental gymnastics that makes the code hard
to read and understand. on the other hand, 8 means something to me.
more importantly, it implies that the code would work with NBBY
of 10 or 12. (c standard says you can't have < 8 §5.2.4.2.1.)
i'd bet there are many things in the code that depend on the sizeof
a byte that don't reference NBBY.
so this define goes 0 fer 2. it can't be changed and it is not informative.
> Similar definitions have been in Unix system headers for
> decades. CHAR_BIT is defined in <limits.h>. (Yes, I know
> there is a difference between a char and a byte. Less well
> known, there is a difference between a byte and an octet.)
this mightn't be the right place to defend a practice by saying that
"unix systems have been doing it for years."
- erik
next prev parent reply other threads:[~2007-09-19 11:51 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-16 18:55 Francisco J Ballesteros
2007-09-16 20:42 ` Anant Narayanan
2007-09-16 21:24 ` Francisco J Ballesteros
2007-09-17 15:22 ` Douglas A. Gwyn
2007-09-16 20:43 ` roger peppe
2007-09-16 20:53 ` Steve Simon
2007-09-17 15:22 ` Douglas A. Gwyn
2007-09-17 20:00 ` Scott Schwartz
2007-09-17 3:23 ` erik quanstrom
2007-09-17 15:22 ` Douglas A. Gwyn
2007-09-17 15:55 ` erik quanstrom
2007-09-18 8:38 ` Douglas A. Gwyn
2007-09-18 10:45 ` dave.l
2007-09-18 14:44 ` Iruata Souza
2007-09-18 15:41 ` Douglas A. Gwyn
2007-09-18 21:34 ` Iruata Souza
2007-10-10 3:30 ` Jack Johnson
2007-10-10 4:02 ` erik quanstrom
2007-10-10 6:17 ` Jack Johnson
2007-10-10 12:22 ` erik quanstrom
2007-09-18 15:27 ` Rob Pike
2007-09-18 15:38 ` Uriel
2007-09-19 8:50 ` Douglas A. Gwyn
2007-09-19 11:51 ` erik quanstrom [this message]
2007-09-19 15:02 ` Russ Cox
2007-09-19 14:17 ` Charles Forsyth
2007-09-19 14:21 ` Iruata Souza
2007-09-19 15:32 ` Skip Tavakkolian
2007-10-09 20:08 ` Aharon Robbins
2007-10-09 21:08 ` Uriel
2007-10-10 5:33 ` sqweek
2007-10-10 11:49 ` erik quanstrom
2007-09-17 14:52 ` ron minnich
2007-09-17 14:53 ` ron minnich
2007-10-10 7:36 John Stalker
2007-10-10 8:24 ` Charles Forsyth
2007-10-10 11:47 ` erik quanstrom
2007-10-10 14:05 ` John Stalker
2007-10-10 14:29 ` erik quanstrom
2007-10-10 15:26 ` John Stalker
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=c1ee80d3c2b50c2b12d22a11d7d703dc@quanstro.net \
--to=quanstro@quanstro.net \
--cc=9fans@cse.psu.edu \
/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 NNTP newsgroup(s).