《Exceptional C++》：C++编程难题与解决方案

PDF文件

下载需积分: 9 | 18.67MB | 更新于2024-07-20 | 181 浏览量 | 举报收藏

立即下载

"Addison Wesley的《Exceptional C++》是一本专注于C++编程难题、问题与解决方案的专业书籍，由Herb Sutter撰写。该书通过实例展示了如何在标准C++中进行稳健的软件工程实践。适合喜欢解决棘手C++问题和谜题，以及致力于编写健壮且可扩展代码的读者。书中问题来源于著名的互联网新闻组comp.lang.c++.moderated中的Guru of the Week栏目，并根据ISO/ANSI C++标准进行了扩展和更新。每个问题都按难度评级，旨在揭示微妙的编程错误或设计考量。在尝试解决问题后，书中会分析代码，指出问题所在，并展示如何修复。涵盖的主题包括模板、异常处理、STL、设计模式等C++核心概念。" 《Exceptional C++》这本书深入探讨了C++语言的高级特性和最佳实践，帮助读者提升编程技巧。作者Herb Sutter是C++社区的重要人物，他的见解对于理解和优化C++代码具有很高的权威性。书中的47个工程难题和编程问题，既有趣味性，又有教育意义，能够挑战读者的思维并提高他们的编程能力。书中涉及的C++主题广泛，包括： 1. **模板(Templates)**：讨论了模板的元编程、模板特化和模板元编程的复杂性，以及如何有效地使用模板来实现泛型编程。 2. **异常处理(Exception Handling)**：讲解了何时、如何以及为什么使用异常处理，以及异常安全性的概念，帮助读者编写能够正确处理异常情况的代码。 3. **STL(Standard Template Library)**：深入解析了容器、迭代器、算法和函数对象，强调了STL在C++编程中的重要性及其高效性。 4. **设计模式(Design Patterns)**：介绍了如何在C++中应用面向对象设计模式，如工厂模式、单例模式和观察者模式，以提高代码的可读性和可维护性。 5. **内存管理(Memory Management)**：探讨了指针操作、动态内存分配和释放，以及如何避免常见的内存泄漏和悬挂指针问题。 6. **命名空间(Namespaces)**：解释了如何通过命名空间来组织代码，防止命名冲突，提高代码的模块化。 7. **C++标准库(The C++ Standard Library)**：展示了标准库提供的各种工具和组件，如iostream库、string类和智能指针。每个问题的分析部分不仅揭示了错误，还提供了改进代码的策略，有助于读者理解C++的底层机制，从而写出更高效、更安全的代码。通过阅读《Exceptional 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页未读，继续阅读

aitazhixin

粉丝: 31

《Exceptional C++》：C++编程难题与解决方案

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

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

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

Addison Wesley Excep

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

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

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

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

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

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

Addison-Wesley.NET. Programer.Windows.Security

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

Exceptional C++

Exceptional.C++

More Exceptional C++

Exceptional_C++

深入理解C++编程：《Exceptional C++》和《More Exceptional C++》解析

深入探索Exceptional C++编程技巧与实践

IOS EXTantion

w3777-xigua-cloud-16804-1756630294228.zip

最新资源