Rationale of enforcing some operators to be members

by

The four operators mentioned in the original posting, =, (), -> and [], must indeed be implemented as non-static member functions (by respectively C++98 §13.5.3/1, §13.5.4/1, §13.5.5/1 and §13.5.6/1).

Bjarne Stroustrup’s rationale was, as I recall from earlier debates on the subject, to retain some sanity in the language, i.e. having at least some things you could rely on no matter how much Someone Else has screwed up by defining non-member operators for existing classes.

I’m not sure I completely agree that the restriction really helps with that, but.

EDIT: I consulted Bjarne Stroustrup about this (he’s always helpful) but it appears that the apparent inconsistencies of the rules are no more than a case of frozen historical accident. He notes that “It looks worse now than it was then because our rules for lvalues and references have changed since the overloading rules were formulated. I tried to look into this issue again a couple of years ago, but ran out of time before producing a complete proposal.”

Cheers & hth.,

PS: “The Design and Evolution of C++” book is great for this kind of question, but unfortunately I don’t have it.

More Related Contents:

  1. What are the basic rules and idioms for operator overloading?
  2. How should I write ISO C++ Standard conformant custom new and delete operators?
  3. Overloading member access operators ->, .*
  4. Why would one replace default new and delete operators?
  5. How do I prevent a class from being allocated via the ‘new’ operator? (I’d like to ensure my RAII class is always allocated on the stack.)
  6. Where and why do I have to put the “template” and “typename” keywords?
  7. What is this weird colon-member (” : “) syntax in the constructor?
  8. overloading friend operator
  9. Can a class member function template be virtual?
  10. What is a “span” and when should I use one?
  11. What does T&& (double ampersand) mean in C++11?
  12. What is std::move(), and when should it be used?
  13. Operator overloading : member function vs. non-member function?
  14. Polymorphism in C++
  15. What is the correct answer for cout
  16. Is the practice of returning a C++ reference variable evil?
  17. What are template deduction guides and when should we use them?
  18. Why does volatile exist?
  19. Different floating point result with optimization enabled – compiler bug?
  20. Why doesn’t a derived template class have access to a base template class’ identifiers?
  21. What is the (“spaceship”, three-way comparison) operator in C++?
  22. What’s the meaning of * and & when applied to variable names?
  23. Operator Overloading in C++ as int + obj
  24. Passing shared pointers as arguments
  25. C++ template friend operator overloading
  26. Why is “operator void” not invoked with cast syntax?
  27. Implicit conversion when overloading operators for template classes
  28. Conversion from Derived** to Base**
  29. Why we need to return reference to istream/ostream while overloading >> and
  30. What is the order of evaluation in a member initializer list?

Leave a Comment