From: Steve Kilbane <steve@whitecrow.demon.co.uk>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] no const?
Date: Wed, 13 Sep 2000 19:11:28 +0200 [thread overview]
Message-ID: <200009131811.TAA15840@whitecrow.demon.co.uk> (raw)
In-Reply-To: Your message of "Wed, 13 Sep 2000 19:03:00 +0200." <029101c01da4$7923b840$89c584c3@cybercable.fr>
Classic Boyd:
> it's a self evident proof that plan 9 works without them.
Sigh, no. You can't prove it works. You can only prove it hasn't
broken so far.
As for unnecessary, this is also true of most things in the language.
Indeed, it's true of the language itself, but that's taking things to
ridiculous levels. The question is, are they worthwhile? I.e., does the
effort of putting them into the compiler pay off in bug avoidance?
> the mess you can make with those 'storage classes' is not understandable.
Question: are you arguing against the concepts of volatile and const,
or against their meanings in ANSI C?
steve
next prev parent reply other threads:[~2000-09-13 17:11 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 [this message]
2000-09-13 19:33 ` Boyd Roberts
2000-09-14 8:13 ` Douglas A. Gwyn
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=200009131811.TAA15840@whitecrow.demon.co.uk \
--to=steve@whitecrow.demon.co.uk \
--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).