Sign In Start Free Trial
Account

Add to playlist

Create a Playlist

Modal Close icon
You need to login to use this feature.
  • Book Overview & Buying Refactoring with C++
  • Table Of Contents Toc
  • Feedback & Rating feedback
Refactoring with C++

Refactoring with C++

By : Dmitry Danilov
5 (2)
close
close
Refactoring with C++

Refactoring with C++

5 (2)
By: Dmitry Danilov

Overview of this book

Despite the prevalence of higher-level languages, C++ is still running the world, from bare-metal embedded systems to distributed cloud-native systems. C++ is on the frontline whenever there is a need for a performance-sensitive tool supporting complex data structures. The language has been actively evolving for the last two decades. This book is a comprehensive guide that shows you how to implement SOLID principles and refactor legacy code using the modern features and approaches of C++, the standard library, Boost library collection, and Guidelines Support Library by Microsoft. The book begins by describing the essential elements of writing clean code and discussing object-oriented programming in C++. You’ll explore the design principles of software testing with examples of using popular unit testing frameworks such as Google Test. The book also guides you through applying automated tools for static and dynamic code analysis using Clang Tools. By the end of this book, you’ll be proficient in applying industry-approved coding practices to design clean, sustainable, and readable real-world C++ code.
Table of Contents (18 chapters)
close
close

Improving Pointer Safety with not_null and std::optional

In C++, pointers are a fundamental part of the language, allowing direct memory access and manipulation. However, the flexibility that pointers offer comes with certain risks and challenges. Here, we’ll explore how modern C++ techniques can enhance pointer safety.

The pitfalls of raw pointers

Raw pointers, while powerful, can be a double-edged sword. They provide no information about the ownership of the object they point to, and they can easily become “dangling” pointers, pointing to memory that has been deallocated. Dereferencing a null or dangling pointer leads to undefined behavior, which can result in hard-to-diagnose bugs.

Using not_null from the Guidelines Support Library

The not_null wrapper provided by the Guidelines Support Library (GSL) aims to overcome the challenges associated with raw pointers. By using not_null, you can clearly signal that a pointer should never be null:

#include...

Unlock full access

Continue reading for free

A Packt free trial gives you instant online access to our library of over 7000 practical eBooks and videos, constantly updated with the latest in tech
bookmark search playlist download font-size

Change the font size

margin-width

Change margin width

day-mode

Change background colour

Close icon Search
Country selected

Close icon Your notes and bookmarks

Delete Bookmark

Modal Close icon
Are you sure you want to delete it?
Cancel
Yes, Delete

Confirmation

Modal Close icon
claim successful

Buy this book with your credits?

Modal Close icon
Are you sure you want to buy this book with one of your credits?
Close
YES, BUY