From: Steve Kilbane <steve@whitecrow.demon.co.uk>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] no const?
Date: Thu, 14 Sep 2000 21:41:48 +0200 [thread overview]
Message-ID: <200009142041.VAA19586@whitecrow.demon.co.uk> (raw)
In-Reply-To: Your message of "Wed, 13 Sep 2000 21:33:33 +0200." <02c301c01db9$8141c3e0$89c584c3@cybercable.fr>
> > Sigh, no. You can't prove it works. You can only prove it hasn't
> > broken so far.
>
> yes, i do know that one.
that's all right, then. we'll ignore the "proof" thing, then. :-)
> but, i does work without them there is
> a subtle difference. ie. they were unnecessay,
Again, no. *you* might not need them. Plus, of course, there's the
distinction between Plan 9 the operating system, and Plan 9 as an
environment. Application programmers are traditionally less sophistocated
than kernel developments, and the ratio of support tools varies accordingly.
> whereas 'if' is
> indispensable.
Uh-uh. 'if' in C is a lot easier than coding in assembler with branches,
but indispensible? The trade-off is just more noticable to you. There's
an IOCCC entry, IIRC, that avoids 'if' completely.
In other words, it's a subjective thing.
> > Question: are you arguing against the concepts of volatile and const,
> > or against their meanings in ANSI C?
>
> 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' :-).
Well, I can't argue beyond this point: I know that 'const' in ANSI C
doesn't mean quite what it should, and avoid using it for that reason
(I particularly dislike not being able to remember whereabouts in the
decl the damn thing should appear).
> well it wouldn't be me if it wasn't 'Classic Boyd'...
I can argue with this one, too... :-)
steve
next prev parent reply other threads:[~2000-09-14 19:41 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
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 [this message]
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=200009142041.VAA19586@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).