From: "Douglas A. Gwyn" <DAGwyn@null.net>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] no const?
Date: Thu, 14 Sep 2000 08:13:10 +0000 [thread overview]
Message-ID: <39BFF408.BF3B8EE@null.net> (raw)
In-Reply-To: <02c301c01db9$8141c3e0$89c584c3@cybercable.fr>
Boyd Roberts wrote:
> the real problem is how it was done in ANSI C. i've got nothing
> against constants. i've even been known to use the odd constant,
> but never a 'const' :-).
Since "const" doesn't mean "constant", again it's evident that
you're criticizing something that you do not understand.
> volatile? yeah, i remember times when i coulda used it. like in
> the 8th ed tu-16 tape driver that john mackin and i fixed.
> volatile would been nice, but we fixed it with a macro (no assembler).
I don't know the specific problem you encountered, but the PDP-11
PCC had a specific hack to disable optimization for certain kinds
of access that could be identified as potentially within the I/O
page. I don't recall whether Ritchie's compiler performed the
optimization in the first place.
> i don't see that polluting the language in such a deplorable way
> is valid.
If you had better suggestions for how to address the same issues,
the C standards committee would have been glad to hear them.
It's easy to complain about what others do, but also pointless.
next prev parent reply other threads:[~2000-09-14 8:13 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-09-13 14:00 David L Rubin
2000-09-13 14:17 ` Boyd Roberts
2000-09-13 16:42 ` Douglas A. Gwyn
2000-09-13 17:03 ` Boyd Roberts
2000-09-13 17:11 ` Steve Kilbane
2000-09-13 19:33 ` Boyd Roberts
2000-09-14 8:13 ` Douglas A. Gwyn [this message]
2000-09-14 12:34 ` Boyd Roberts
2000-09-15 8:47 ` Douglas A. Gwyn
2000-09-15 11:34 ` Boyd Roberts
2000-09-15 13:07 ` Theo Honohan
2000-09-15 14:55 ` Boyd Roberts
2000-09-16 8:51 ` Matt Lawless
2000-09-18 10:47 ` Douglas A. Gwyn
2000-09-15 20:46 ` Steve Kilbane
2000-09-14 19:41 ` Steve Kilbane
2000-09-18 10:47 ` Douglas A. Gwyn
2000-09-13 14:22 Russ Cox
2000-09-13 14:30 ` Boyd Roberts
2000-09-13 14:29 miller
2000-09-13 14:39 forsyth
2000-09-13 16:44 ` Douglas A. Gwyn
2000-09-13 18:06 Russ Cox
2000-09-14 8:13 ` Douglas A. Gwyn
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=39BFF408.BF3B8EE@null.net \
--to=dagwyn@null.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).