C++17权威指南：2019最新版详解

需积分: 5 94 浏览量更新于2024-06-27 收藏 2.22MB PDF 举报

《C++17 - The Complete Guide》是由Nicolai M. Josuttis撰写的一本详尽的指南，针对C++17语言版本提供了全面深入的介绍。本书的第一版于2019年12月20日发布，作者保留所有版权，任何未经授权的复制、存储、检索或任何形式的传输都是被禁止的。这本书是使用LaTeX文档处理系统排版的，旨在为读者提供最新和最实用的C++17语言知识。该书内容包括以下几个部分： 1. **前言**：这部分可能会介绍作者的写作背景、编写本书的目的以及读者群体，同时也可能概述C++17相对于之前版本的重要改进和新特性。 2. **本书版本**：列出本书的不同版本更新情况，确保读者了解他们所阅读的是哪个具体版本，可能有针对C++17标准更新的特别说明。 3. **致谢**：感谢了在编写过程中给予帮助和支持的人，可能是同行、编辑、审稿人或者社区成员。 4. **关于本书**：这部分会详细介绍书籍的目标、内容结构，以及作者对学习C++17读者的预期背景知识，例如他们应具备的编程基础和C++语言经验。 5. **阅读指南**：如何有效地利用本书进行学习，可能包含推荐的学习路径、习题解答的使用方法以及在线资源的链接。 6. **错误术语**：为了帮助读者理解，书中可能解释了一些编程术语和概念，确保他们能准确理解和应用C++17的特性和用法。 7. **目录**：详细的章节列表，涵盖了C++17语言的关键特性如通用元编程、异步/并行编程、新类型系统、以及对C++标准库的重大更新等内容。 8. **主体内容**：每一章深入剖析C++17的具体特性，通过实例演示、代码示例和详细解析来讲解，使读者能够掌握新功能的使用和潜在的最佳实践。 9. **后续支持与销售信息**：告知读者可以在哪里购买电子版或纸质版，以及Leanpub平台如何支持作者与读者之间的互动和反馈迭代。《C++17 - The Complete Guide》是一本面向C++开发者的实用指南，旨在帮助读者充分利用C++17语言的新功能，提升编程技能，并适应不断演进的编程世界。通过本书，读者不仅能学到语言规范，还能学习到如何有效地在实际项目中应用这些新特性。

Josuttis: C++17 2019/12/20 17:30 page xvi

xvi Preface

• 2019-05-30: Large quantity of ﬁxes following feedback and reviews

• 2019-05-29: Fix of over-aligned heap memory and more due to C++17 given training

• 2019-05-12: Addition of “placement delete” for over-aligned heap memory

• 2019-05-02: Description of the new value of __cplusplus

• 2019-04-26: Description of all new type traits and std::invoke()

• 2019-04-24: Description of the motivation for problems of std::launder()

• 2019-04-24: merge() for associative/unordered containers

• 2019-04-23: Publication of a new electronic version with several ﬁxes and improvements

• 2019-04-23: Adoption of a standard ﬁx of create_directory()

• 2019-04-22: try_emplace() and insert_or_assign() for (unordered) maps

• 2019-04-21: data() for strings

• 2019-03-28: Detailed documentation of all new (parallel) STL algorithms

• 2019-03-18: uncaught_exceptions()

• 2019-03-10: Large number of small ﬁxes due to reader feedback

• 2019-02-14: accumulate() versus reduce() versus transform_reduce()

• 2019-02-12: for_each_n() algorithm

• 2019-02-12: sample() algorithm

• 2019-02-11: clamp() utility function

• 2019-02-03: Execution policies and list of parallel algorithms

• 2019-02-02: Documentation of round-trip support of to_chars() and from_chars()

• 2019-01-11: New examples with performance measurements on parallel algorithms

• 2018-12-26: Polymorphism with std::variant<>

• 2018-12-25: Using std::tie() for structured bindings

• 2018-12-24: Description of Boyer-Moore(-Horspool) searchers

• 2018-11-24: Description of generic size(), empty(), data()

• 2018-10-14: Publication of a new electronic version with several ﬁxes and improvements

• 2018-08-14: Addition of polymorphic memory resources (pmr)

• 2018-08-07: Addition of as_const()

• 2018-07-15: Filesystem library chapter fully written

• 2018-05-30: Addition of scoped_lock and shared_mutex

• 2018-05-29: Addition of is_always_lock_free() and hardware interference sizes

• 2018-05-28: Addition of variable templates with placeholders

• 2018-05-27: Addition of container support for incomplete types

• 2018-05-11: Addition of node handles for associative and unordered containers

• 2018-05-11: First full supported example of parallel algorithms on ﬁlesystems

• 2018-04-04: Beginning of an initial introduction of (new) parallel algorithms

• 2018-04-03: Improvements to std::optional<> and more about the Filesystem library

• 2018-03-15: Publication of a new electronic version with a couple of small ﬁxes

• 2018-01-12: Publication of a new electronic version with several ﬁxes and improvements

Josuttis: C++17 2019/12/20 17:30 page xvii

Acknowledgments xvii

• 2018-01-11: Addition of new attribute features

• 2018-01-03: Addition of new attributes

• 2018-01-02: Addition of new and delete with over-aligned data

• 2017-12-25: Publication of a new electronic version with several ﬁxes and improvements

• 2017-12-24: Addition of exception speciﬁcations becoming part of the type

• 2017-12-23: Addition of u8 preﬁx for UTF-8 character literals

• 2017-12-22: Addition of hexadecimal ﬂoating-point literals

• 2017-12-15: Publication of the ﬁrst electronic version

Acknowledgments

First of all I would like to thank you, the C++ community, for making this book possible. The incredible

design of new features, the helpful feedback, and the curiosity are the basis for the evolution of a successful

language. In particular, thanks for all the issues you told me about and explained and for the feedback you

gave.

I would especially like to thank everyone who reviewed drafts of this book or corresponding slides and

provided valuable feedback and clariﬁcation. These reviews increased the quality of the book signiﬁcantly

again proving that good things need the input of many “wise guys.” For this reason, so far (this list is still

growing) huge thanks to Roland Bock, Marshall Clow, Matthew Dodkins, Javier Estrada, Andreas Fertig,

Bartlomiej Filipek, Davis Herring, Tom Honermann, Thomas, K

oppe, Daniel Kr

ugler, Graham Haynes,

Austin McCartney, Alex Nash, Billy O’Neal, Paul Reilly, Barry Revzin, Vittorio Romeo, David Sankel, Tim

Song, Zachary Turner, and Tony Van Eerd.

In addition, I would like to thank everyone in the C++ community and on the C++ standardization com-

mittee. In addition to all the work involved in adding new language and library features, these experts

spent many, many hours explaining and discussing their work with me, and they did so with patience and

enthusiasm.

Special thanks go to the LaTeX community for a great text system and to Frank Mittelbach for solving

my L

X issues (it was almost always my fault).

And ﬁnally, many thanks go to my proofreader, Tracey Duffy, who has done a tremendous job of con-

verting my “German English” into native English.

Josuttis: C++17 2019/12/20 17:30 page xix

About This Book

C++17 is the next evolution in modern C++ programming, which is already at least partially supported by

the latest version of gcc, clang, and Visual C++. Although the move to C++17 is not as big a step as the move

to C++11, C++17 contains a large number of small and valuable language and library features that again

will change the way we program in C++. This applies to both application programmers and programmers

who provide foundation libraries.

This book will present all the new language and library features in C++17. It will cover the motivation

and context of each new feature with examples and background information. As usual for my books, the

focus lies on the application of the new features in practice and the book will demonstrate how features

impact day-to-day programming and how you can beneﬁt from them in projects.

What You Should Know Before Reading This Book

To get the most from this book, you should already be familiar with C++, ideally C++11 and/or C++14.

However, you do not have to be an expert. My goal is to make the content understandable for the average

C++ programmer, not necessarily knowing all details of the latest features. You should be familiar with

the concepts of classes and inheritance, and you should be able to write C++ programs using components

such as IOstreams and containers from the C++ standard library. You should also be familiar with the basic

features of “Modern C++”, such as auto, decltype, move semantics, and lambdas.

Nevertheless, I will discuss basic features and review more subtle issues as the need arises, even when

such issues are not directly related to C++17. This ensures that the text is accessible to experts and interme-

diate programmers alike.

Note that I usually use the modern form of initialization (introduced in C++11 as uniform initialization)

with curly braces:

int i{42};

std::string s{"hello"};

This form of initialization, which is called list initialization, has the advantage that it can be used with fun-

damental types, class types, aggregates (extended with C++17), enumeration types (added with C++17), and

auto (ﬁxed with C++17) and is able to detect narrowing errors (e.g., initialization of an int by a ﬂoating-

xix

Josuttis: C++17 2019/12/20 17:30 page xx

xx About This Book

point value). If the braces are empty, the default constructors of (sub)objects are called and fundamental

data types are initialized with 0/false/nullptr.

Overall Structure of the Book

This book covers all changes to C++ introduced with C++17. This applies to both language and library

features as well as both features that affect day-to-day application programming and features for the sophis-

ticated implementation of (foundation) libraries. However, the more general cases and examples usually

come ﬁrst.

The different chapters are grouped, but the grouping has no deeper didactic reasoning other than that it

makes sense to ﬁrst introduce language features because they might be used by the following library features.

In principle, you can read the chapters in any order. If features from different chapters are combined, there

are corresponding cross-references.

As a result, the book contains the following parts:

• Part I covers the new non-template language features.

• Part II covers the new language features for generic programming with templates.

• Part III introduces the new standard library components.

• Part IV covers the extensions and modiﬁcations to the existing components of the standard library.

• Part V covers language and library features for experts such as foundation library programmers.

• Part VI contains some concluding general hints about C++17.

How to Read This Book

In my experience, the best way to learn something new is to look at examples. Therefore, you will ﬁnd

a lot of examples throughout the book. Some are just a few lines of code illustrating an abstract concept,

whereas others are complete programs that provide a concrete application of the material. The latter kind of

examples will be introduced by a C++ comment describing the ﬁle containing the program code. You can

ﬁnd these ﬁles on the website for this book at http://www.cppstd17.com.

Error Terminology

Note that I often talk about programming errors. If there is no special hint, the term error or a comment

such as

... // ERROR

means a compile-time error. The corresponding code should not compile (with a conforming compiler).

If I use the term runtime error, the program might compile but not behave correctly or result in undeﬁned

behavior (thus, it might or might not do what is expected).

The only exception are atomic data types (type std::atomic<>), where even list initialization does not guarantee

proper initialization. This will hopefully be ﬁxed with C++20.

剩余451页未读，继续阅读

承让@

粉丝: 8
资源: 380

C++17权威指南：2019最新版详解

C++17: the complete guide

C++17 The Complete Guide.pdf

c++ 17 the complete guide

C++Templates-The.Complete.Guide.pdf

C++ Templates-The Complete Guide.pdf

c++17 - the complete guide pdf

C++ Templates - The Complete Guide英文版.rar

C++.Templates.-.The Complete.Guide(侯捷译)

c++ templates - the complete guide, 2nd edition pdf github

Crystal Reports 9 - The Complete Reference.part1

最新资源