Suppose we implement the += operator as shown in the following. What goes wrong with b += b ? void bag::operator +=(const bag& addend) // Library facilities used: cassert { size_type i; // An array index assert(size( ) + addend.size( ) <= CAPACITY); for (i = 0; i < addend.used; ++i) { data[used] = addend.data[i]; ++used; } } Group of answer choices If we activate b += b, then the private member variable size is the same variable as addend.size. The size( ) + addend.size( ) is less than CAPACITY. So the program after the assert statement will be executed. If we activate b += b, then the private member variable size is the same variable as addend.size. The size( ) + addend.size( ) is larger than CAPACITY. So the program after the assert statement will not have chance to be executed. If we activate b += b, then the private member variable used is the same variable as addend.used. Each iteration of the loop adds 1 to used, and hence addend.used is also increasing, and the loop will be terminated earlier than expected. If we activate b += b, then the private member variable used is the same variable as addend.used. Each iteration of the loop adds 1 to used, and hence addend.used is also increasing, and the loop never ends. There is no problem at all.

Computer Networking: A Top-Down Approach (7th Edition)

7th Edition

ISBN:9780133594140

Author:James Kurose, Keith Ross

Publisher:James Kurose, Keith Ross

Chapter1: Computer Networks And The Internet

Section: Chapter Questions

Problem R1RQ: What is the difference between a host and an end system? List several different types of end...

See similar textbooks

Related questions

Question

Suppose we implement the += operator as shown in the following. What goes wrong with b += b ?

void bag::operator +=(const bag& addend)

// Library facilities used: cassert
{
    size_type i; // An array index
    assert(size( ) + addend.size( ) <= CAPACITY);
    for (i = 0; i < addend.used; ++i)
    {
         data[used] = addend.data[i];
         ++used;
     }
}

Group of answer choices

If we activate b += b, then the private member variable size is the same variable as addend.size. The size( ) + addend.size( ) is less than CAPACITY. So the program after the assert statement will be executed.

If we activate b += b, then the private member variable size is the same variable as addend.size. The size( ) + addend.size( ) is larger than CAPACITY. So the program after the assert statement will not have chance to be executed.

If we activate b += b, then the private member variable used is the same variable as addend.used. Each iteration of the loop adds 1 to used, and hence addend.used is also increasing, and the loop will be terminated earlier than expected.

There is no problem at all.

Expert Solution

Trending now

This is a popular solution!

Step by step

Solved in 4 steps

SEE SOLUTION Check out a sample Q&A here

Knowledge Booster

Learn more about

Need a deep-dive on the concept behind this application? Look no further. Learn more about this topic, computer-engineering and related others by exploring similar questions and additional content below.

Recommended textbooks for you

Computer Networking: A Top-Down Approach (7th Edi…

Computer Engineering

ISBN:

9780133594140

Author:

James Kurose, Keith Ross

Publisher:

PEARSON