From: "Steve Graegert" <graegerts@gmail.com>
To: Shriramana Sharma <jamadagni@gmail.com>
Cc: linux-c-programming@vger.kernel.org
Subject: Re: efficiency in passing a value to a function
Date: Wed, 4 Apr 2007 20:38:36 +0200 [thread overview]
Message-ID: <6a00c8d50704041138l278f34d2t9c97ba551f7ad5c3@mail.gmail.com> (raw)
In-Reply-To: <4613DCB8.8030007@gmail.com>
Shriramana,
On 4/4/07, Shriramana Sharma <jamadagni@gmail.com> wrote:
> Hello.
>
> Is providing an input to a function by constant reference more efficient
> than passing it by value? In what way.
>
> For ex:
>
> int addOne ( const & int inValue ) { return inValue + 1 ; }
>
> vs:
>
> int addOne ( int inValue ) { return inValue + 1 ; }
>
> or:
>
> void printThis ( const & int inValue ) { cout << inValue ; }
>
> vs:
>
> void printThis ( int inValue ) { cout << inValue ; }
>
> I think passing as const & would be more efficient since passing by
> value would involve copying the value whereas passing by const & would
> skip this step. Am I right? Or is there something else?
I have seen many programs making use const reference parameters in
order to inform the compiler that the parameter is read-only, and
hence should be better optimized.
Unfortunately, this intent is at odds with the C++ language
definition. The const keyword says that the storage may not be
modified through the given name. What it does not say is that the
storage cannot be modified through some other name.
With the exception of variables directly declared const, which means
you can only initialize them, const is basically ineffective a
improving run-time performance. It does, however, catch errors in the
programming process.
\Steve
--
Steve Grägert <steve@graegert.com>
Jabber xmpp://graegerts@jabber.org
Internet http://eth0.graegert.com, http://blog.graegert.com
-
To unsubscribe from this list: send the line "unsubscribe linux-c-programming" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2007-04-04 18:38 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-04 17:13 efficiency in passing a value to a function Shriramana Sharma
2007-04-04 18:27 ` Glynn Clements
2007-04-11 21:44 ` Adam Dyga
2007-04-04 18:38 ` Steve Graegert [this message]
2007-04-05 12:05 ` Glynn Clements
2007-04-05 13:02 ` Steve Graegert
2007-04-08 15:17 ` Shriramana Sharma
2007-04-13 17:23 ` Glynn Clements
2007-04-14 13:15 ` Adam Dyga
2007-04-08 14:45 ` Shriramana Sharma
2007-04-13 17:51 ` Glynn Clements
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=6a00c8d50704041138l278f34d2t9c97ba551f7ad5c3@mail.gmail.com \
--to=graegerts@gmail.com \
--cc=jamadagni@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).