J. Davidson - Beautiful C++: 30 Core Guidelines for Writing Clean, Safe, and Fast Code

Pearson is dedicated to creating bias-free content that reflects the diversity of all learners. We embrace the many dimensions of diversity, including but not limited to race, ethnicity, gender, socioeconomic status, ability, age, sexual orientation, and religious or political beliefs.

Education is a powerful force for equity and change in our world. It has the potential to deliver opportunities that improve lives and enable economic mobility. As we work with authors to create content for every product and service, we acknowledge our responsibility to demonstrate inclusivity and incorporate diverse scholarship so that everyone can achieve their potential through learning. As the worlds leading learning company, we have a duty to help drive change and live up to our purpose to help more people create a better life for themselves and to create a better world.

Our ambition is to purposefully contribute to a world where:

• Everyone has an equitable and lifelong opportunity to succeed through learning.

• Our educational products and services are inclusive and represent the rich diversity of learners.

• Our educational content accurately reflects the histories and experiences of the learners we serve.

• Our educational content prompts deeper discussions with learners and motivates them to expand their own learning (and worldview).

While we work hard to present unbiased content, we want to hear from you about any concerns or needs with this Pearson product so that we can investigate and address them.

• Please contact us with concerns about any potential bias at https://www.pearson.com/report-bias.html.

P.2: Write in ISO Standard C++ ()

https://isocpp.github.io/CppCoreGuidelines/CppCoreGuidelines#Rp-Cplusplus

P.4: Ideally, a program should be statically type safe ()

https://isocpp.github.io/CppCoreGuidelines/CppCoreGuidelines#Rp-typesafe

P.10: Prefer immutable data to mutable data ()

https://isocpp.github.io/CppCoreGuidelines/CppCoreGuidelines#Rp-mutable

P.11: Encapsulate messy constructs, rather than spreading through the code ()

https://isocpp.github.io/CppCoreGuidelines/CppCoreGuidelines#Rp-library

I.3: Avoid singletons ()

https://isocpp.github.io/CppCoreGuidelines/CppCoreGuidelines#Ri-singleton

I.11: Never transfer ownership by a raw pointer (T*) or reference (T&) ()

https://isocpp.github.io/CppCoreGuidelines/CppCoreGuidelines#Ri-raw

I.23: Keep the number of function arguments low ()

https://isocpp.github.io/CppCoreGuidelines/CppCoreGuidelines#Ri-nargs

I.26: If you want a cross-compiler ABI, use a C-style subset ()

https://isocpp.github.io/CppCoreGuidelines/CppCoreGuidelines#Ri-abi

I.30: Encapsulate rule violations ()

https://isocpp.github.io/CppCoreGuidelines/CppCoreGuidelines#Ri-encapsulate

F.21: To return multiple out values, prefer returning a struct or tuple

()

https://isocpp.github.io/CppCoreGuidelines/CppCoreGuidelines#Rf-out-multi

F.51: Where there is a choice, prefer default arguments over overloading

()

https://isocpp.github.io/CppCoreGuidelines/CppCoreGuidelines#Rf-default-args

C.45: Dont define a default constructor that only initializes data members; use in-class member initializers instead ()

https://isocpp.github.io/CppCoreGuidelines/CppCoreGuidelines#Rc-default