《Exceptional C++》：探索C++编程与工程难题

4星 · 超过85%的资源需积分: 10 20 浏览量更新于2024-07-23 收藏 18.67MB PDF 举报

"Exceptional C++: 47 Engineering Puzzles, Programming Problems, and Solutions" 这本书，《Exceptional C++》，是Herb Sutter所著，由Addison-Wesley出版社出版，于1999年11月18日发行，拥有240页的内容，ISBN号为0-201-61562-2。这本书是计算机科学领域的经典著作，特别关注标准C++的软件工程实践。书中的核心在于通过47个工程难题、编程问题和解决方案，帮助读者提升C++编程技能并培养编写健壮和可扩展代码的能力。作者Herb Sutter是一位知名的C++专家，他在书中设置了一系列棘手的C++设计和编程挑战，旨在让读者在解决这些问题的过程中，不仅得到娱乐，还能磨练自己的编程技艺。每个问题根据难度进行了评级，旨在揭示微妙的编程错误或设计考量。在读者尝试自己解决问题后，书中会深入分析代码，指出其中的问题，并展示如何正确地修复它们。这些问题很多来源于著名的互联网新闻组comp.lang.c++.moderated中的“Guru of the Week”特色栏目，这些内容已经过扩展和更新，以符合官方的ISO/ANSI C++标准。通过阅读《Exceptional C++》，读者可以深入理解C++的陷阱和最佳实践，学习如何避免常见的编程错误，以及如何利用C++的特性来构建高效且可维护的代码。这本书不仅适合经验丰富的C++程序员用来提升自己的技能，也适合初学者作为深入理解语言特性和最佳实践的教材。此外，Herb Sutter在书中探讨的问题和解决方案不仅涉及语法和技术层面，还涵盖了设计模式、异常处理、模板元编程、STL（标准模板库）使用等高级主题。通过解决这些难题，读者将能够更好地理解和掌握C++的复杂性，从而在实际项目中更游刃有余。《Exceptional C++》是一本深入而全面的C++指南，它鼓励读者思考和实践，从而成为更出色的C++程序员。通过这本书，读者不仅可以学习到标准C++的关键知识，还能提升对编程和软件工程原则的理解。

I l

@ve RuBoard

•

Table of Contents

Exceptional C++: 47 Engineering Puzzles,

Programming Problems, and Solutions

Herb Sutter

Publisher

: Addison Wesley

Pub Date : November 18, 1999

ISBN

: 0-201-61562-2

Pages

: 240

Exceptional C++

shows by example how to go about sound software engineering in standard C++. Do

you enjoy solving thorny C++ problems and puzzles? Do you relish writing robust and extensible

code? Then take a few minutes and challenge yourself with some tough C++ design and programming

problems.

The puzzles and problems in

Exceptional C++

not only entertain, they will help you hone your skills to

become the sharpest C++ programmer you can be. Many of these problems are culled from the

famous Guru of the Week feature of the Internet newsgroup comp.lang.c++.moderated, expanded

and updated to conform to the official ISO/ANSI C++ Standard.

Each problem is rated according to difficulty and is designed to illustrate subtle programming mistakes

or design considerations. After you've had a chance to attempt a solution yourself, the book then

dissects the code, illustrates what went wrong, and shows how the problem can be fixed. Covering a

broad range of C++ topics, the problems and solutions address critical issues such as:

Generic programming and how to write reusable templates

Exception safety issues and techniques

Robust class design and inheritance

Compiler firewalls and the Pimpl Idiom

Name lookup, namespaces, and the Interface Principle

Memory management issues and techniques

Traps, pitfalls, and anti-idioms

Optimization

Try your skills against the C++ masters and come away with the insight and experience to create

I l

@ve RuBoard

Item 1. Iterators

Difficulty: 7

Every programmer who uses the standard library has to be aware of these common and not-so-

common iterator mistakes. How many of them can you find?

The following program has at least four iterator-related problems. How many can you find?

int main()

{

vector<Date> e;

copy( istream_iterator<Date>( cin ),

istream_iterator<Date>(),

back_inserter( e ) );

vector<Date>::iterator first =

find( e.begin(), e.end(), "01/01/95" );

vector<Date>::iterator last =

find( e.begin(), e.end(), "12/31/95" );

*last = "12/30/95";

copy( first,

last,

ostream_iterator<Date>( cout, "\n" ) );

e.insert( --e.end(), TodaysDate() );

copy( first,

last,

ostream_iterator<Date>( cout, "\n" ) );

}

I l

@ve RuBoard

I l

@ve RuBoard

•

Table of Contents

Exceptional C++: 47 Engineering Puzzles,

Programming Problems, and Solutions

Herb Sutter

Publisher

: Addison Wesley

Pub Date : November 18, 1999

ISBN

: 0-201-61562-2

Pages

: 240

Exceptional C++

shows by example how to go about sound software engineering in standard C++. Do

you enjoy solving thorny C++ problems and puzzles? Do you relish writing robust and extensible

code? Then take a few minutes and challenge yourself with some tough C++ design and programming

problems.

The puzzles and problems in

Exceptional C++

not only entertain, they will help you hone your skills to

become the sharpest C++ programmer you can be. Many of these problems are culled from the

famous Guru of the Week feature of the Internet newsgroup comp.lang.c++.moderated, expanded

and updated to conform to the official ISO/ANSI C++ Standard.

Each problem is rated according to difficulty and is designed to illustrate subtle programming mistakes

or design considerations. After you've had a chance to attempt a solution yourself, the book then

dissects the code, illustrates what went wrong, and shows how the problem can be fixed. Covering a

broad range of C++ topics, the problems and solutions address critical issues such as:

Generic programming and how to write reusable templates

Exception safety issues and techniques

Robust class design and inheritance

Compiler firewalls and the Pimpl Idiom

Name lookup, namespaces, and the Interface Principle

Memory management issues and techniques

Traps, pitfalls, and anti-idioms

Optimization

Try your skills against the C++ masters and come away with the insight and experience to create

I l

@ve RuBoard

Solution

int main()

{

vector<Date> e;

copy( istream_iterator<Date>( cin ),

istream_iterator<Date>(),

back_inserter( e ) );

This is fine so far. The Date class writer provided an extractor function with the signature

operator>>( istream&, Date& ), which is what istream_iterator<Date> uses to read the

Dates from the

cin

stream. The

copy()

algorithm just stuffs the Dates into the vector.

vector<Date>::iterator first =

find( e.begin(), e.end(),

01/01/95

);

vector<Date>::iterator last =

find( e.begin(), e.end(),

12/31/95

);

*last = "12/30/95";

Error: This may be illegal, because last may be

e.end()

and therefore not a dereferenceable

iterator.

The

find()

algorithm returns its second argument (the end iterator of the range) if the value is not

found. In this case, if "12/31/95" is not in

, then last is equal to

e.end()

, which points to one-

past-the-end of the container and is not a valid iterator.

copy(

first,

last,

ostream_iterator<Date>( cout,

) );

Error: This may be illegal because [first,last) may not be a valid range; indeed, first may

actually be after last

For example, if "01/01/95" is not found in

but "12/31/95" is, then the iterator last will point to

something earlier in the collection (the Date object equal to "12/31/95") than does the iterator first

(one past the end). However,

copy()

requires that first must point to an earlier place in the same

collection as

last—that is, [first

last) must be a valid range.

Unless you're using a checked version of the standard library that can detect some of these problems

for you, the likely symptom if this happens will be a difficult-to-diagnose core dump during or

sometime after the

copy()

e.insert(--e.end()

, TodaysDate() );

First error: The expression "

--e.end()

" is likely to be illegal.

The reason is simple, if a little obscure: On popular implementations of the standard library,

vector<Date>::iterator is often simply a Date*, and the C++ language doesn't allow you to

modify temporaries of builtin type. For example, the following plain-jane code is also illegal:

I l

@ve RuBoard

•

Table of Contents

Exceptional C++: 47 Engineering Puzzles,

Programming Problems, and Solutions

Herb Sutter

Publisher

: Addison Wesley

Pub Date : November 18, 1999

ISBN

: 0-201-61562-2

Pages

: 240

Exceptional C++

shows by example how to go about sound software engineering in standard C++. Do

you enjoy solving thorny C++ problems and puzzles? Do you relish writing robust and extensible

code? Then take a few minutes and challenge yourself with some tough C++ design and programming

problems.

The puzzles and problems in

Exceptional C++

not only entertain, they will help you hone your skills to

become the sharpest C++ programmer you can be. Many of these problems are culled from the

famous Guru of the Week feature of the Internet newsgroup comp.lang.c++.moderated, expanded

and updated to conform to the official ISO/ANSI C++ Standard.

Each problem is rated according to difficulty and is designed to illustrate subtle programming mistakes

or design considerations. After you've had a chance to attempt a solution yourself, the book then

dissects the code, illustrates what went wrong, and shows how the problem can be fixed. Covering a

broad range of C++ topics, the problems and solutions address critical issues such as:

Generic programming and how to write reusable templates

Exception safety issues and techniques

Robust class design and inheritance

Compiler firewalls and the Pimpl Idiom

Name lookup, namespaces, and the Interface Principle

Memory management issues and techniques

Traps, pitfalls, and anti-idioms

Optimization

Try your skills against the C++ masters and come away with the insight and experience to create

Date* f(); // function that returns a Date*

p = --f(); // error, but could be "f() - 1"

Fortunately, we know that vector<Date>::iterator is a random-access iterator, so there's no loss

of efficiency in writing this (more) correctly as:

e.insert( e.end() - 1, TodaysDate() );

Second error: Now you still have the other error, which is: If

is empty, any attempt to take "the

iterator before

e.end()

" (whether you spell that "

--e.end()

" or "

e.end()–1

") will not be a valid

iterator.

copy(

first,

last,

ostream_iterator<Date>( cout,

) );

}

Error:

first

and

last may not be valid iterators any more.

vector

grows in "chunks" so that it won't have to reallocate its buffer every time you insert

something into it. However, sometimes the

vector

will be full, and adding something will trigger a

reallocation.

Here, as a result of the e.insert() operation, the vector may or may not grow, which means its

memory may or may not move. Because of this uncertainty, we must consider any existing iterators

into that container to be invalidated. In this case, if the memory really did move, then the buggy

copy()

will again generally manifest as a difficult-to-diagnose core dump.

Guideline

Never dereference an invalid iterator.

To summarize: When using iterators, be aware of four main issues.

Valid values: Is the iterator dereferenceable? For example, writing "

*e.end()

" is always a

programming error.

Valid lifetimes: Is the iterator still valid when it's being used? Or has it been invalidated by some

operation since we obtained it?

Valid ranges: Is a pair of iterators a valid range? Is first really before (or equal to) last

? Do

both really point into the same container?

Illegal builtin manipulation: For example, is the code trying to modify a temporary of builtin

type, as in "

--e.end()

" above? (Fortunately, the compiler can often catch this kind of mistake

for you, and for iterators of class type, the library author will often choose to allow this sort of

thing for syntactic convenience.)

I l

@ve RuBoard

I l

@ve RuBoard

•

Table of Contents

Exceptional C++: 47 Engineering Puzzles,

Programming Problems, and Solutions

Herb Sutter

Publisher

: Addison Wesley

Pub Date : November 18, 1999

ISBN

: 0-201-61562-2

Pages

: 240

Exceptional C++

shows by example how to go about sound software engineering in standard C++. Do

you enjoy solving thorny C++ problems and puzzles? Do you relish writing robust and extensible

code? Then take a few minutes and challenge yourself with some tough C++ design and programming

problems.

The puzzles and problems in

Exceptional C++

not only entertain, they will help you hone your skills to

become the sharpest C++ programmer you can be. Many of these problems are culled from the

famous Guru of the Week feature of the Internet newsgroup comp.lang.c++.moderated, expanded

and updated to conform to the official ISO/ANSI C++ Standard.

Each problem is rated according to difficulty and is designed to illustrate subtle programming mistakes

or design considerations. After you've had a chance to attempt a solution yourself, the book then

dissects the code, illustrates what went wrong, and shows how the problem can be fixed. Covering a

broad range of C++ topics, the problems and solutions address critical issues such as:

Generic programming and how to write reusable templates

Exception safety issues and techniques

Robust class design and inheritance

Compiler firewalls and the Pimpl Idiom

Name lookup, namespaces, and the Interface Principle

Memory management issues and techniques

Traps, pitfalls, and anti-idioms

Optimization

Try your skills against the C++ masters and come away with the insight and experience to create

I l

@ve RuBoard

Item 2. Case-Insensitive Strings—Part 1

Difficulty: 7

So you want a case-insensitive string class? Your mission, should you choose to accept it, is to write

one.

This Item is composed of three related points.

What does "

case-insensitive

" mean?

Write a

ci_string

class that is identical to the standard std::string class but that is case-

insensitive in the same way as the commonly provided extension

stricmp()

[1]

ci_string

should be usable as follows:

[1]

The

stricmp()

case-insensitive string comparison function is not part of the C or C++

standards, but it is a common extension on many C and C++ compilers.

ci_string s( "AbCdE" );

// case insensitive

assert( s == "abcde" );

assert( s == "ABCDE" );

// still case-preserving, of course

assert( strcmp( s.c_str(), "AbCdE" ) == 0 );

assert( strcmp( s.c_str(), "abcde" ) != 0 );

Is making case sensitivity a property of the object a good idea?

I l

@ve RuBoard

I l

@ve RuBoard

•

Table of Contents

Exceptional C++: 47 Engineering Puzzles,

Programming Problems, and Solutions

Herb Sutter

Publisher

: Addison Wesley

Pub Date : November 18, 1999

ISBN

: 0-201-61562-2

Pages

: 240

Exceptional C++

shows by example how to go about sound software engineering in standard C++. Do

you enjoy solving thorny C++ problems and puzzles? Do you relish writing robust and extensible

code? Then take a few minutes and challenge yourself with some tough C++ design and programming

problems.

The puzzles and problems in

Exceptional C++

not only entertain, they will help you hone your skills to

become the sharpest C++ programmer you can be. Many of these problems are culled from the

famous Guru of the Week feature of the Internet newsgroup comp.lang.c++.moderated, expanded

and updated to conform to the official ISO/ANSI C++ Standard.

Each problem is rated according to difficulty and is designed to illustrate subtle programming mistakes

or design considerations. After you've had a chance to attempt a solution yourself, the book then

dissects the code, illustrates what went wrong, and shows how the problem can be fixed. Covering a

broad range of C++ topics, the problems and solutions address critical issues such as:

Generic programming and how to write reusable templates

Exception safety issues and techniques

Robust class design and inheritance

Compiler firewalls and the Pimpl Idiom

Name lookup, namespaces, and the Interface Principle

Memory management issues and techniques

Traps, pitfalls, and anti-idioms

Optimization

Try your skills against the C++ masters and come away with the insight and experience to create

I l

@ve RuBoard

Solution

The answers to the three questions are as follows.

What does "

case-insensitive

" mean?

What "

case-insensitive

" actually means depends entirely on your application and language. For

example, many languages do not have cases at all. For those that do, you still have to decide

whether you want accented characters to compare equal to unaccented characters, and so on.

This Item provides guidance on how to implement case-insensitivity for standard strings in

whatever sense applies to your situation.

Write a

ci_string

class that is identical to the standard std::string class but that is case-

insensitive in the same way as the commonly provided extension

stricmp()

The "how can I make a case-insensitive string?" question is so common that it probably

deserves its own FAQ—hence this Item.

Here's what we want to achieve:

ci_string s(

AbCdE

);

// case insensitive

assert( s ==

abcde

);

assert( s ==

ABCDE

);

// still case-preserving, of course

assert( strcmp( s.c_str(),

AbCdE

) == 0 );

assert( strcmp( s.c_str(),

abcde

) != 0 );

The key here is to understand what a

string

actually is in Standard C++. If you look in your

trusty

string

header, you'll see something like this:

typedef basic_string<char> string;

string

isn't really a class; it's a

typedef

of a template. In turn, the

basic_string<>

template is declared as follows, possibly with additional implementation-specific template

parameters:

template<class charT,

class traits = char_traits<charT>,

class Allocator = allocator<charT> >

class basic_string;

So "

string

" really means "basic_string<char, char_traits<char>, allocator<char>

," possibly with additional defaulted template parameters specific to the implementation you're

using. We don't need to worry about the

allocator

part, but the key here is the char_traits

part, because char_traits defines how characters interact—and compare!

So let's compare

string

basic_string supplies useful comparison functions that let you

compare whether one

string

is equal to another, less than another, and so on. These

string

剩余250页未读，继续阅读

WangLanguager

粉丝: 1w+
资源: 300

《Exceptional C++》：探索C++编程与工程难题

[计算机科学经典著作].Addison.Wesley.-.Exceptional.C++.rar

[计算机科学经典著作].Addison.Wesley.-.More.Exceptional.C..rar

[计算机科学经典着作].Addison.Wesley.-.Exceptional.C++.pdf

[计算机科学经典著作].Addison.Wesley.-.More.Exceptional.C++.pdf

Addison.Wesley.Exceptional.C++ - 47 Engineering Puzzles, Programming Problems, and Solutions.chm

Addison.Wesley.Exceptional.C++.Style.40.New.Engineering.Puzzles,.Programming.Problems.and.Solutio.chm

Addison Wesley Exceptional C

vc编程系列之Addison Wesley - Exceptional C++

vc编程系列之Addison Wesley - More Exceptional C++

Addison.Wesley.Advanced.Programming.in.the.UNIX.Environment.Second.Edition.chm

最新资源