Errata

Hello,

(The problem does not concern page 4, but chapter 4 examples. I haven't browsed the other chapters
yet.)

The uses of stream.eof() and getline are incorrect. The lines should be read with:
while(std::getline(in, tmp, '
'))

see http://www.parashift.com/c++-faq-lite/input-output.html#faq-15.5

"To delete the executable and the intermediate object file from the makefile directory, enter make clean."

I don't think there is any intermediate object file being created with this Makefile, and even if there is, make will only delete the executable when the clean target is specified:

clean:
rm -f hello

(The top of p. 68 correctly states that only hello (the executable) is deleted.)

The output shown for example 3-4 should be:
There are 3 ways to do this.
There are Those cost $50.
abc123

rather than:
There are 3 ways to do this.
Those cost $50.
abc123

I ran this example and researched the boost format.hpp and discovered that the code line f.clear()
clears the bound items not the object f as it was declared. so the no bound items. so everything
from %1% on in the declaration of f is cleared.

I compiled the code on MinGW 3.4.2 compiler using Eclipse CDT as my IDE.

The function
void split(...)
you show in this example will fail, if the string does not contain the separator character. The resulting vector<string> will not contain any entries, while I would expect it to contain one entry, the full input string.
A possible solution (add lines marked with a +):
void split(const string& s, char c,
vector<string>& v) {
string::size_type i = 0;
string::size_type j = s.find(c);

+ if (j == string::npos) {
+ v.push_back(s);
+ return;
+ }

while (j != string::npos) {
// ... the while loop as in the example
}
}

the comment "// Recipe 4.7" should refer to 4.6, i.e. should read
"// Recipe 4.6"

As is, this code generates malloc errors when run, the reason being that the recursive delete tries
to delete a pointer that is really a pass by reference.

This can be fixed by using

TreeNode<string>* node1 = new TreeNode<string>("frank");
....

node1->addChild(node2);

This problem, however, is something that might merit discussion as it had me confused for a bit.

Newer versions of gcc (3.4 and above) require "typename" to be inserted before
vector<valT>::const_iterator in the declaration of the for loop.

original:
for (vector<valT>::const_iterator p = v.begin( );
changes to:
for (typename vector<valT>::const_iterator p = v.begin( );

This is in reference to "10.9 Creating a Temporary Filename and File".

The example recommends using the function tmpnam to create a unique file name. Using this function is discouraged. See the man page.
tmpnam -- "Never use this function. Use mkstemp(3) instead."

This is in reference to "10.9 Creating a Temporary Filename and File".

The example recommends using the function tmpnam to create a unique file name. Using this function is discouraged. See the man page.
tmpnam -- "Never use this function. Use mkstemp(3) instead."

TEXT IS:
explicit matrix(const valarray<T>& x)

SHOULD BE:
explicit matrix(const std::valarray<T>& x)

The variable declaration "init_" in the struct Conn:
static boost::once_flag init_
should be
static boost::once_flag initFlag_
as per the description and discussion on page 463 after the second paragraph.

Similarly the starting values should be set to the correct name:
boost::once_flag Conn::initFlag_ = BOOST_ONCE_INIT;
and the call inside the worker function should be:
boost::call_once(Conn::init, Conn::initFlag_);

It would be easier just to change the discussion on page 463, but from the discussion it's clear that "initFlag_" is a better name than "init_".

Characters callback function is now -
void characters(const XMLCh* const chars, const XMLSize_t length)
for Xerces 3.1.1

SAX2 ErrorHandler requires -
using namespace xercesc;

"The purpose of DTDs is to identify the subset of well-formed XML documents that are interesting in a certain application domain."

This is wrong, well-formedness (i.e. if an XML instance is syntactically correct) can be checked without any document grammar since well-formedness is a part of the XML specification. However, validity can only be checked with a grammar such as a DTD or an XSD at hand.

The same mistake is on page 520, Discussion, 1st paragraph:
"The purpose of a schema is to identify the subset of well-formed XML documents that are interesting in a certain application domain."

The example is "Adding support for serialization to the class Animal...", but the
example code shows "class Contact".
The code should be "class Animal"

Initialisation order of ival_,sval_ generates -Wreorder warning in some compilers
Members sval_ and ival_ are private when they should be public. Example will not compile (even with Error line commented out). Fix is to move declarations to public: section.