is that correct to write a constructor like this?
class A
{
A(const A& a)
{
....
}
};
if yes, then is it correct to invoke it like this:
A* other;
...
A* instance = new A(*(other));
if not, what do you suggest?
Thanks
Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
Almost correct. When declaring the constructor in the class, simply write
A, notA::A; you would useA::Awhen giving a definition for the constructor outside of the class declaration. Otherwise, yes.Also, as James points out, unless you are copying from an object that you are accessing via a pointer, you don’t need to do any dereferencing (if it is a value or a reference). One typically does not use pointers unless it is necessary to do so. On that principle, you would have something like:
Note, though, that the first statement
A xinvokes the default constructor. C++ will provide a default implementation of that constructor, but it might not be what you want and even if it is what you want, it is better style, IMHO, to give one explicitly to let other programmers know that you’ve thought about it.Edit
C++ will automatically provide an implementation of the default constructor, but only if you don’t provide any user-defined constructors — once you provide a constructor of your own, the compiler won’t automatically generate the default constructor. Truth be told, I forgot about this as I’ve been in the habit of giving all constructor definitions myself, even when they aren’t strictly necessary. In C++0x, it will be possible to use
= default, which will provide the simplicity of using the compiler-generated constructor while at the same time making the intention to use it clear to other developers.