Is this key-oriented access-protection pattern a known idiom?

by

Thanks to your other question it looks like this pattern is now known as the “passkey” pattern.

In C++11, it gets even cleaner, because instead of calling

b.protectedMethod(SomeKey());

you can just call:

b.protectedMethod({});

More Related Contents:

  1. Can we increase the re-usability of this key-oriented access-protection pattern?
  2. clean C++ granular friend equivalent? (Answer: Attorney-Client Idiom)
  3. How to name this key-oriented access-protection pattern?
  4. C++ Singleton design pattern
  5. Is Meyers’ implementation of the Singleton pattern thread safe?
  6. Singleton: How should it be used
  7. What’s the scope of inline friend functions?
  8. Why does C# not provide the C++ style ‘friend’ keyword? [closed]
  9. How to declare a templated struct/class as a friend?
  10. Can any one provide me a sample of Singleton in c++?
  11. What is Proxy Class in C++
  12. Singleton instance declared as static variable of GetInstance method, is it thread-safe? [duplicate]
  13. Are inner classes in C++ automatically friends?
  14. declare template friend function of template class
  15. ampersand (&) at the end of variable etc
  16. Friend scope in C++
  17. Generating an interface without virtual functions?
  18. boost::asio and Active Object
  19. friend class with limited access
  20. ‘friend’ functions and
  21. friend AND inline method, what’s the point ?
  22. Is it bad practice to allocate memory in a DLL and give a pointer to it to a client app?
  23. Why does a C++ friend class need a forward declaration only in other namespaces?
  24. Memory management patterns in C++
  25. a class-key must be declared when declaring a friend
  26. How does the friend keyword (Class/Function) break encapsulation in C++?
  27. Decorator pattern in C++
  28. Double dispatch/multimethods in C++
  29. Specify a class member function as a friend of another class?
  30. friend declaration declares a non-template function [duplicate]

Leave a Comment