Free Shipping to all UK customers for orders over £25.00

0 Total items on my wish-list.

Free Shipping to all UK customers for orders over £25.00

Ryefieldbooks Logo

Ryefield Books

Free Shipping to all UK customers for orders over £25.00

Ryefieldbooks Logo

Ryefield Books

© Copyright Ryefield Books - All Right Reserved
Product Categories
My Shopping Cart
Void image

You shopping cart is empty

You may browse our offerings to locate what you're
searching for, then put it in your shopping cart.

Book cover image

100 C++ Mistakes and How to Avoid Them

By  Rich Yonts

Usually dispatched within 3 - 5 business days.

In Stock (10)

£ 58.49

Description

Learn how to handle errors, inefficiencies, and outdated paradigms by exploring the most common mistakes you'';ll find in production C++ code. 100 C++ Mistakes and How To Avoid Them reveals the problems you''ll inevitably encounter as you write new C++ code and diagnose legacy applications, along with practical techniques you need to resolve them. Inside 100 C++ Mistakes and How To Avoid Them you''ll learn how to: Design solid classes Minimize resource allocation/deallocation issues Use new C++ features Identify the differences between compile and runtime issues Recognize C-style idioms that miss C++ functionality Use exceptions well 100 C++ Mistakes and How To Avoid Them gives you practical insights and techniques to improve your C++ coding kung fu. Author Rich Yonts has been using C++ since its invention in the 1980s. This book distills that experience into practical, reusable advice on how C++ programmers at any skill level can improve their code. Unlike many C++ books that concentrate on language theory and toy exercises, this book is loaded with real examples from production codebases. About the technology: Over ten billion lines of C++ code are running in production applications, and 98-developers find and fix mistakes in them every day. Even mission-critical applications have bugs, performance inefficiencies, and readability problems. This book will help you identify them in the code you'';re maintaining and avoid them in the code you'';re writing.