linux-c-programming.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Steve Graegert" <graegerts@gmail.com>
To: linux-c-programming@vger.kernel.org
Subject: Re: Need for const in function argument list
Date: Sun, 26 Mar 2006 10:57:44 +0000	[thread overview]
Message-ID: <6a00c8d50603260257u18642532l7b88ae11c86e46cb@mail.gmail.com> (raw)
In-Reply-To: <200603261614.39708.samjnaa@gmail.com>

On 3/26/06, Shriramana Sharma <samjnaa@gmail.com> wrote:
> In the Qt constructor for the DateTime class, I see:
>
> QDateTime::QDateTime(const QDate &date)
>
> what is the need for the keyword const here? If it is to indicate that the
> date variable does not change, then in very many such places should the const
> keyword be used. But it is not.

You've answered your own question.  If there is no const in places
where it should be there can be three reasons: (a) either the
developer have forgotten to mark the parameters const or (b) the code
has been written before ANSI C where the const keyword was not known. 
Most sophisticated libraries provide properly designed functions, so I
am sure, (c) they have had their reasons not to "const" in some
places.

> As a related question, in the syntax for printf, we have printf(const char
> *format) -- why should we have const here?

Because the format (the string to display) is provided as a constant
expression and it is not being modified:

	printf("%s\n", "abc");
	printf("%s\n", mystring);

In both cases the format argument is a constant string.

	\Steve

  reply	other threads:[~2006-03-26 10:57 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-26 10:44 Need for const in function argument list Shriramana Sharma
2006-03-26 10:57 ` Steve Graegert [this message]
2006-03-26 13:38   ` Shriramana Sharma
2006-03-26 15:38     ` Steve Graegert
2006-03-26 16:27     ` Glynn Clements
2006-03-27  8:25       ` Yorgos Pagles

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=6a00c8d50603260257u18642532l7b88ae11c86e46cb@mail.gmail.com \
    --to=graegerts@gmail.com \
    --cc=linux-c-programming@vger.kernel.org \
    /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).