Effective C++ Item 23 Prefer non-member non-friend functions to member functions

by

Access to the book is by no mean necessary.

The issues we are dealing here are Dependency and Reuse.

In a well-designed software, you try to isolate items from one another so as to reduce Dependencies, because Dependencies are a hurdle to overcome when change is necessary.

In a well-designed software, you apply the DRY principle (Don’t Repeat Yourself) because when a change is necessary, it’s painful and error-prone to have to repeat it in a dozen different places.

The “classic” OO mindset is increasingly bad at handling dependencies. By having lots and lots of methods depending directly on the internals of the class, the slightest change implies a whole rewrite. It need not be so.

In C++, the STL (not the whole standard library), has been designed with the explicit goals of:

  • cutting dependencies
  • allowing reuse

Therefore, the Containers expose well-defined interfaces that hide their internal representations but still offer sufficient access to the information they encapsulate so that Algorithms may be executed on them. All modifications are made through the container interface so that the invariants are guaranteed.

For example, if you think about the requirements of the sort algorithm. For the implementation used (in general) by the STL, it requires (from the container):

  • efficient access to an item at a given index: Random Access
  • the ability to swap two items: not Associative

Thus, any container that provides Random Access and is not Associative is (in theory) suitable to be sorted efficiently by (say) a Quick Sort algorithm.

What are the Containers in C++ that satisfy this ?

  • the basic C-array
  • deque
  • vector

And any container that you may write if you pay attention to these details.

It would be wasteful, wouldn’t it, to rewrite (copy/paste/tweak) sort for each of those ?

Note, for example, that there is a std::list::sort method. Why ? Because std::list does not offer random access (informally myList[4] does not work), thus the sort from algorithm is not suitable.

More Related Contents:

  1. Operator overloading : member function vs. non-member function?
  2. Free function versus member function
  3. Information Hiding VS Encapsulation
  4. What is the difference between public, private, and protected inheritance in C++?
  5. When should you use ‘friend’ in C++?
  6. What are all the member-functions created by compiler for a class? Does that happen all the time?
  7. Can I access private members from outside the class without using friends?
  8. How to access private data members outside the class without making “friend”s? [duplicate]
  9. How to directly bind a member function to an std::function in Visual Studio 11?
  10. accessing a protected member of a base class in another subclass
  11. Nonstatic member as a default argument of a nonstatic member function [duplicate]
  12. Print address of virtual member function
  13. What is the meaning of ‘const’ at the end of a member function declaration?
  14. Do non-static member variables in a C++ struct/class need to be marked as volatile to be treated as volatile in a member function?
  15. C++ crash on getting pointer [closed]
  16. How to use C++ in Go
  17. How do C++ class members get initialized if I don’t do it explicitly?
  18. Difference between string and char[] types in C++
  19. Can we reassign the reference in C++?
  20. Is there a way to pass auto as an argument in C++?
  21. How to define a C++ preprocessor macro through the command line with CMake?
  22. Why/when is __declspec( dllimport ) not needed?
  23. How can I reliably get an object’s address when operator& is overloaded?
  24. C++ How is release-and-acquire achieved on x86 only using MOV?
  25. C++ error: ‘_mm_sin_ps’ was not declared in this scope
  26. Visual c++ “for each” portability
  27. Disabling Warnings generated via _CRT_SECURE_NO_DEPRECATE
  28. fatal error C1083: Cannot open include file: ‘xyz.h’: No such file or directory?
  29. convert string to integer in c++
  30. Calling a function through its address in memory in c / c++

Leave a Comment