Question on Copy constructor!!

[prashna]

Hi all,
Why is it necessary to declare a parameter to a copy constructor as a
reference?Thanks in Advance

[Rolf Magnus]

prashna wrote:

Hi all,
Why is it necessary to declare a parameter to a copy constructor as a
reference?Thanks in Advance

Think of what happens if it's not a reference. The value gets passed as
a copy. But to get passed as a copy, the copy constructor would be
called. That copy constructor gets its value by copy, so the copy
constructor must be called, for which the copy constructor would need
to be called, which needs.... you get the point. It produces an
infinite recursion of copy constructor calls.

[Jerry Coffin]

va******@rediffmail.com (prashna) wrote in message news:<d4**************************@posting.google. com>...

Hi all,
Why is it necessary to declare a parameter to a copy constructor as a
reference?Thanks in Advance

Because taking its argument by value would cause infinite recursion
(when you pass something by value, you're passing a copy of the
original item...)

This basic question has plagued computer science for decades. I'm
pretty sure it was at least 30 years ago that this question came up
wrt Lisp, prompting a paper named something like "Should cons cons its
inputs?". The answer was basically the same, but back then it took a
whole paper to say "pass by reference must be used to avoid infinite
recursion." :-)
--
Later,
Jerry.

The universe is a figment of its own imagination.

[Ajay Baranwal]

Rolf Magnus <ra******@t-online.de> wrote in message news:<c7*************@news.t-online.com>...

prashna wrote:

Hi all,
Why is it necessary to declare a parameter to a copy constructor as a
reference?Thanks in Advance

Think of what happens if it's not a reference. The value gets passed as
a copy. But to get passed as a copy, the copy constructor would be
called. That copy constructor gets its value by copy, so the copy
constructor must be called, for which the copy constructor would need
to be called, which needs.... you get the point. It produces an
infinite recursion of copy constructor calls.

Further to add, why can't we have the parameter to be a pointer ? I
believe then we need to copy each of the data members in the object
pointed by the pointer. And that's safe. No infinite recursion. But it
could be a dangling or uninitialized pointer coming as parameter which
would give core dump when try to access the real object!

Thanks!

[Karthik]

prashna wrote:

Hi all,
Why is it necessary to declare a parameter to a copy constructor as a
reference?Thanks in Advance

Else, it does not make sense for the code generator.

Consider a function like this -

1- void fun ( X fun )
2- void fun ( X & fun)

What essentially happens is that, in case 1, a copy of object X is
created (copy constructor is invoked, if X is a user-defined data type)
pushed onto the function stack, and operated on.

In case 2, a reference of the object instead of the object is pushed
onto the stack.
Coming back to copy constructor -
Assume you have X ( X ) as the signature of copy constructor, you would
eseentially get into an infinite loop generating the code ( or in other
words, it does not make sense to do so).
But X ( X & ) is fine.

This is explained in detail in the book - 'C++ programming language'
written by the author of C++, Stroustroup.. Grab one if you are into C++.
--
Karthik.
Humans please 'removeme_' for my real email.