9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "Douglas A. Gwyn" <DAGwyn@null.net>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] no const?
Date: Mon, 18 Sep 2000 10:47:05 +0000	[thread overview]
Message-ID: <39C30B5E.617F0721@null.net> (raw)
In-Reply-To: <200009142041.VAA19586@whitecrow.demon.co.uk>

Steve Kilbane wrote:
> 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).

"const" does mean what it should, just as "char" means what it should.
The names may be misleading if you have no other clue, but you're not
supposed to be guessing about the language.

The "const" qualifier goes next to the thing it qualifies.
How hard is that rule to remember?
	const int *p;	// pointer to const int
	int const *p;	// pointer to const int
	int *const p;	// const pointer to int



  reply	other threads:[~2000-09-18 10:47 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
2000-09-18 10:47             ` Douglas A. Gwyn [this message]
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=39C30B5E.617F0721@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).