Free Test Overloading assignment... – C++ Lan...

Q1: Which operator is overloaded for assignment in C++?

A. operator= B. operator== C. operator+= D. operator++

Q2: Can the assignment operator (=) be overloaded as a non-member function?

A. Yes B. No C. Only for built-in types D. Only for friend functions

Q3: What is the recommended return type of an overloaded assignment operator?

A. ClassName& B. void C. ClassName D. int

Q4: Why should you check for self-assignment in operator=?

A. To avoid deleting the object's own data B. To optimize speed C. To allocate memory D. To convert types

Q5: What is a typical first step in overloading operator=?

A. Check self-assignment B. Allocate memory C. Call destructor D. Return void

Q6: In a class with dynamically allocated memory, what should operator= do?

A. Deep copy the data B. Shallow copy C. Ignore pointers D. Call default assignment

Q7: Which of these is the correct operator= signature?

A. ClassName& operator=(const ClassName& rhs); B. void operator=(ClassName rhs); C. ClassName operator=(ClassName& rhs); D. int operator=(const ClassName& rhs);

Q8: What should operator= return?

A. *this B. void C. nullptr D. New object

Q9: Which keyword can help access private members in operator= if defined outside the class?

A. friend B. static C. virtual D. inline

Q10: When overloading operator=, why is the parameter passed as const reference?

A. To avoid unnecessary copying B. To allow modification C. For speed D. It's mandatory

Q11: Can operator= be overloaded for built-in types?

A. No B. Yes C. Only for pointers D. Only for references

Q12: Is it necessary to explicitly define operator= if no dynamic memory is used?

A. No, compiler provides default B. Yes, always required C. Only for const objects D. Only for pointers

Q13: Which of these is a common mistake in operator= overloading?

A. Not checking self-assignment B. Returning a reference C. Passing const reference parameter D. Calling delete

Q14: What should you do before assigning new data in operator=?

A. Release existing resources B. Allocate new memory only C. Copy data blindly D. Return void

Q15: How do you handle exceptions in operator=?

A. Use try-catch or copy-and-swap idiom B. Ignore exceptions C. Throw from operator= D. Return false

Q16: What is the copy-and-swap idiom?

A. Use a copy of the object and swap data B. Directly assign pointers C. Use move semantics D. Ignore the old data

Q17: Which method improves exception safety in operator=?

A. Copy-and-swap B. Returning void C. Throwing exceptions D. Using raw pointers

Q18: Can operator= be overloaded for const objects?

A. No B. Yes C. Only if mutable members D. Only for pointers

Q19: What happens if operator= returns void?

A. Chained assignments not possible B. Compiles fine C. Increases performance D. Prevents self-assignment

Quiz for Overloading assignment operator