From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@cse.psu.edu, Russ Cox <rsc@swtch.com>
Subject: Re: [9fans] const
Date: Wed, 7 Dec 2005 07:01:07 -0600 [thread overview]
Message-ID: <20051207130107.224496A9@dexter-peak.quanstro.net> (raw)
In-Reply-To: <ee9e417a0512070417u3f06fc48i2fe4323c571bd564@mail.gmail.com>
i've found const pretty useful, dispite the fact it does create some inconsistencies.
it's chief virtue is that you can tell without looking any further than the prototype
that a function that takes a const char* makes it's own copy, if it needs one.
if you're careful with const, i think it can be a help in preventing some silly mistakes
that will cause a benign looking program to get up and fandango on core.
unfortunately, glibc, for example, is not very consistant. dispite the fact that it returns
a pointer into envp, glibc getenv is declared as "char* getenv(const char*);".
- erik
Russ Cox <rsc@swtch.com> writes
|
| > I'm trying to find a reference to a tirade against
| > the C const type qualifier. I think it was writtent
| > during the ANSI-isation of C by dmr or perhaps bwk,
| > (or was it was rob).
|
| http://www.lysator.liu.se/c/dmr-on-noalias.html
| http://tinyurl.com/8435y
|
| The second (actually a Google Groups url) explains the first.
|
| Russ
next prev parent reply other threads:[~2005-12-07 13:01 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-07 10:34 Steve Simon
2005-12-07 12:17 ` Russ Cox
2005-12-07 13:01 ` erik quanstrom [this message]
[not found] ` <000401c5fb32$64502e00$14aaa8c0@utelsystems.local>
2005-12-07 14:10 ` "Nils O. Selåsdal"
2005-12-07 15:05 ` Steve Simon
2005-12-07 15:30 ` Lucio De Re
2005-12-07 15:53 ` C H Forsyth
[not found] ` <1E68F99F-78D7-4321-BE56-7D0319212596@telus.net>
2005-12-07 16:11 ` "Nils O. Selåsdal"
2005-12-07 17:27 ` Paul Lalonde
2005-12-07 16:23 ` jmk
2005-12-07 17:28 ` Skip Tavakkolian
2005-12-07 18:51 ` Joel Salomon
2005-12-07 18:58 ` Charles Forsyth
2005-12-07 19:30 ` Joel Salomon
2005-12-07 19:36 ` Brantley Coile
2005-12-07 19:51 ` rog
2005-12-07 21:07 ` Charles Forsyth
2005-12-07 21:18 ` Bruce Ellis
2005-12-07 21:22 ` Paul Lalonde
2005-12-07 22:04 ` Rob Pike
2005-12-07 22:44 ` Micah Stetson
2005-12-07 22:44 ` Micah Stetson
2005-12-07 22:46 ` Brantley Coile
2005-12-07 20:33 ` Skip Tavakkolian
2005-12-08 7:39 ` geoff
2005-12-08 7:53 ` Lucio De Re
2005-12-08 7:54 ` geoff
2005-12-08 10:23 ` Bruce Ellis
2005-12-08 15:58 ` Brantley Coile
2005-12-09 1:44 ` geoff
2005-12-09 2:04 ` Russ Cox
2005-12-09 2:19 ` geoff
2005-12-09 9:54 ` Charles Forsyth
2005-12-09 16:25 ` David Leimbach
2005-12-09 16:59 ` Richard Bilson
2005-12-09 17:42 ` David Leimbach
2005-12-09 19:17 ` Richard Bilson
2005-12-09 17:01 ` Ronald G Minnich
2005-12-09 17:39 ` Russ Cox
2005-12-09 17:40 ` [9fans] PCICIA Modem TamTam
2005-12-09 18:59 ` Sascha Retzki
2005-12-12 15:07 ` Paweł Lasek
2005-12-26 9:00 ` Martin C. Atkins
2005-12-26 14:19 ` Paweł Lasek
2005-12-09 19:37 ` [9fans] Re: const Nikita Danilov
2005-12-09 20:30 ` Russ Cox
2005-12-09 20:37 ` Ronald G Minnich
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=20051207130107.224496A9@dexter-peak.quanstro.net \
--to=quanstro@quanstro.net \
--cc=9fans@cse.psu.edu \
--cc=rsc@swtch.com \
/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).