Skip to main content

Assign to all data members in operator=.

Item 16: Assign to all data members in operator=.
Item 45 explains that C++ will write an assignment operator for you if you don't declare one yourself, and Item
11 describes why you often won't much care for the one it writes for you, so perhaps you're wondering if you
can somehow have the best of both worlds, whereby you let C++ generate a default assignment operator and you
selectively override those parts you don't like. No such luck. If you want to take control of any part of the
assignment process, you must do the entire thing yourself.
In practice, this means that you need to assign to every data member of your object when you write your
assignment operator(s):
template
// template for classes associating
class NamedPtr {
// names with pointers (from Item 12)
public:
NamedPtr(const string& initName, T *initPtr);
NamedPtr& operator=(const NamedPtr& rhs);
private:
string name;
T *ptr;
};
template
NamedPtr& NamedPtr::operator=(const NamedPtr& rhs)
{
if (this == &rhs)
return *this;
// see Item 17
// assign to all data members
name = rhs.name;
// assign to name
*ptr = *rhs.ptr;
// for ptr, assign what's
// pointed to, not the
// pointer itself
return *this;
// see Item 15
}
This is easy enough to remember when the class is originally written, but it's equally important that the
assignment operator(s) be updated if new data members are added to the class. For example, if you decide to
upgrade the NamedPtr template to carry a timestamp marking when the name was last changed, you'll have to
add a new data member, and this will require updating the constructor(s) as well as the assignment operator(s).
In the hustle and bustle of upgrading a class and adding new member functions, etc., it's easy to let this kind of
thing slip your mind.
The real fun begins when inheritance joins the party, because a derived class's assignment operator(s) must also
handle assignment of its base class members! Consider this:
class Base {
public:
Base(int initialValue = 0): x(initialValue) {}
private:
int x;
};
class Derived: public Base {
public:
Derived(int initialValue)
: Base(initialValue), y(initialValue) {}
Derived& operator=(const Derived& rhs);
private:
int y;
};
The logical way to write Derived's assignment operator is like this:
// erroneous assignment operator
Derived& Derived::operator=(const Derived& rhs)
{
if (this == &rhs) return *this;
// see Item 17
y = rhs.y;
// assign to Derived's
// lone data member
return *this;
// see Item 15
}
Unfortunately, this is incorrect, because the data member x in the Base part of a Derived object is unaffected by
this assignment operator. For example, consider this code fragment:
void assignmentTester()
{
Derived d1(0);
Derived d2(1);
d1 = d2;
// d1.x = 0, d1.y = 0
// d2.x = 1, d2.y = 1
// d1.x = 0, d1.y = 1!
}
Notice how the Base part of d1 is unchanged by the assignment.
The straightforward way to fix this problem would be to make an assignment to x in Derived::operator=.
Unfortunately, that's not legal, because x is a private member of Base. Instead, you have to make an explicit
assignment to the Base part of Derived from inside Derived's assignment operator.
This is how you do it:
// correct assignment operator
Derived& Derived::operator=(const Derived& rhs)
{
if (this == &rhs) return *this;
Base::operator=(rhs);
y = rhs.y;
// call this->Base::operator=
return *this;
}
Here you just make an explicit call to Base::operator=. That call, like all calls to member functions from within
other member functions, will use *this as its implicit left-hand object. The result will be that Base::operator=
will do whatever work it does on the Base part of *this ? precisely the effect you want.
Alas, some compilers (incorrectly) reject this kind of call to a base class's assignment operator if that
assignment operator was generated by the compiler (see Item 45). To pacify these renegade translators, you need
to implement Derived::operator= this way:
Derived& Derived::operator=(const Derived& rhs)
{
if (this == &rhs) return *this;
static_cast(*this) = rhs;
// call operator= on
// Base part of *this
y = rhs.y;
return *this;
}
This monstrosity casts *this to be a reference to a Base, then makes an assignment to the result of the cast. That
makes an assignment to only the Base part of the Derived object. Careful now! It is important that the cast be to
a reference to a Base object, not to a Base object itself. If you cast *this to be a Base object, you'll end up
calling the copy constructor for Base, and the new object you construct (see Item M19) will be the target of the
assignment; *this will remain unchanged. Hardly what you want.
Regardless of which of these approaches you employ, once you've assigned the Base part of the Derived object,
you then continue with Derived's assignment operator, making assignments to all the data members of Derived.
A similar inheritance-related problem often arises when implementing derived class copy constructors. Take a
look at the following, which is the copy constructor analogue of the code we just examined:
class Base {
public:
Base(int initialValue = 0): x(initialValue) {}
Base(const Base& rhs): x(rhs.x) {}
private:
int x;
};
class Derived: public Base {
public:
Derived(int initialValue)
: Base(initialValue), y(initialValue) {}
Derived(const Derived& rhs)
// erroneous copy
: y(rhs.y) {}
// constructor
private:
int y;
};
Class Derived demonstrates one of the nastiest bugs in all C++-dom: it fails to copy the base class part when a
Derived object is copy constructed. Of course, the Base part of such a Derived object is constructed, but it's
constructed using Base's default constructor. Its member x is initialized to 0 (the default constructor's default
parameter value), regardless of the value of x in the object being copied!
To avoid this problem, Derived's copy constructor must make sure that Base's copy constructor is invoked
instead of Base's default constructor. That's easily done. Just be sure to specify an initializer value for Base in
the member initialization list of Derived's copy constructor:
class Derived: public Base {
public:
Derived(const Derived& rhs): Base(rhs), y(rhs.y) {}
...
};
Now when a client creates a Derived by copying an existing object of that type, its Base part will be copied,
too.

Comments

Popular posts from this blog

OWASP Top 10 Threats and Mitigations Exam - Single Select

Last updated 4 Aug 11 Course Title: OWASP Top 10 Threats and Mitigation Exam Questions - Single Select 1) Which of the following consequences is most likely to occur due to an injection attack? Spoofing Cross-site request forgery Denial of service   Correct Insecure direct object references 2) Your application is created using a language that does not support a clear distinction between code and data. Which vulnerability is most likely to occur in your application? Injection   Correct Insecure direct object references Failure to restrict URL access Insufficient transport layer protection 3) Which of the following scenarios is most likely to cause an injection attack? Unvalidated input is embedded in an instruction stream.   Correct Unvalidated input can be distinguished from valid instructions. A Web application does not validate a client’s access to a resource. A Web action performs an operation on behalf of the user without checking a shared sec

CKA Simulator Kubernetes 1.22

  https://killer.sh Pre Setup Once you've gained access to your terminal it might be wise to spend ~1 minute to setup your environment. You could set these: alias k = kubectl                         # will already be pre-configured export do = "--dry-run=client -o yaml"     # k get pod x $do export now = "--force --grace-period 0"   # k delete pod x $now Vim To make vim use 2 spaces for a tab edit ~/.vimrc to contain: set tabstop=2 set expandtab set shiftwidth=2 More setup suggestions are in the tips section .     Question 1 | Contexts Task weight: 1%   You have access to multiple clusters from your main terminal through kubectl contexts. Write all those context names into /opt/course/1/contexts . Next write a command to display the current context into /opt/course/1/context_default_kubectl.sh , the command should use kubectl . Finally write a second command doing the same thing into /opt/course/1/context_default_no_kubectl.sh , but without the use of k

标 题: 关于Daniel Guo 律师

发信人: q123452017 (水天一色), 信区: I140 标  题: 关于Daniel Guo 律师 关键字: Daniel Guo 发信站: BBS 未名空间站 (Thu Apr 26 02:11:35 2018, 美东) 这些是lz根据亲身经历在 Immigration版上发的帖以及一些关于Daniel Guo 律师的回 帖,希望大家不要被一些马甲帖广告帖所骗,慎重考虑选择律师。 WG 和Guo两家律师对比 1. fully refund的合约上的区别 wegreened家是case不过只要第二次没有file就可以fully refund。郭家是要两次case 没过才给refund,而且只要第二次pl draft好律师就可以不退任何律师费。 2. 回信速度 wegreened家一般24小时内回信。郭律师是在可以快速回复的时候才回复很快,对于需 要时间回复或者是不愿意给出确切答复的时候就回复的比较慢。 比如:lz问过郭律师他们律所在nsc区域最近eb1a的通过率,大家也知道nsc现在杀手如 云,但是郭律师过了两天只回复说让秘书update最近的case然后去网页上查,但是上面 并没有写明tsc还是nsc。 lz还问过郭律师关于准备ps (他要求的文件)的一些问题,模版上有的东西不是很清 楚,但是他一般就是把模版上的东西再copy一遍发过来。 3. 材料区别 (推荐信) 因为我只收到郭律师写的推荐信,所以可以比下两家推荐信 wegreened家推荐信写的比较长,而且每封推荐信会用不同的语气和风格,会包含lz写 的research summary里面的某个方面 郭家四封推荐信都是一个格式,一种语气,连地址,信的称呼都是一样的,怎么看四封 推荐信都是同一个人写出来的。套路基本都是第一段目的,第二段介绍推荐人,第三段 某篇或几篇文章的abstract,最后结论 4. 前期材料准备 wegreened家要按照他们的模版准备一个十几页的research summary。 郭律师在签约之前说的是只需要准备五页左右的summary,但是在lz签完约收到推荐信 ,郭律师又发来一个很长的ps要lz自己填,而且和pl的格式基本差不多。 总结下来,申请自己上心最重要。但是如果选律师,lz更倾向于wegreened,