Home > Articles

C++ Interfaces

This chapter is from the book

This chapter is from the book

C++ Core Guidelines Explained: Best Practices for Modern C++C++ Core Guidelines Explained: Best Practices for Modern C++

Learn More Buy

This chapter is from the book

This chapter is from the book

C++ Core Guidelines Explained: Best Practices for Modern C++C++ Core Guidelines Explained: Best Practices for Modern C++

Learn More Buy

Related rules

I present the rule “I.10: Use exceptions to signal a failure to perform a required task” in Chapter 11, Error Handling, the rule “I.11: Never transfer ownership by a raw pointer (T*) or reference (T&)” in Chapter 4, Functions, the rule “I.22: Avoid complex initialization of global objects” in Chapter 8, Expressions and Statements, and the rule “I.25: Prefer abstract classes as interfaces to class hierarchies” in Chapter 5, Classes and Class Hierarchies.

Distilled: Important

  • Don’t use global variables. They introduce hidden dependencies.

  • Singletons are global variables in disguise.

  • Interfaces and in particular functions should express their intent.

  • Interfaces should be strongly typed and have few arguments that cannot be easily confused.

  • Don’t take a C-array by pointer but use a std::span.

  • If you want to separate the users of a class from its implementation, use the PImpl idiom.

InformIT Promotional Mailings & Special Offers

I would like to receive exclusive offers and hear about products from InformIT and its family of brands. I can unsubscribe at any time.