I know this sounds mean, but whenever they say they spent a decade on a committee, I can almost guarantee you that the next thing they say will be true yet inconsequential.
I say this because I have done my share of proof-reading C and C++ books. And there are a lot of errors. But that's not the worst of it. The worst books don't teach you anything, are full of errors, and the author continues to try to impress you with his work on the standards. The best books teach you and have a few errors that you will figure out on your own.
(I got into the proof-reading and writing biz years ago for a couple of years. How? By writing a letter about how book X was so full of mistakes it was unreadable. So I speak from experience)
I know this sounds mean, but whenever they say they spent a decade on a committee, I can almost guarantee you that the next thing they say will be true yet inconsequential.
I say this because I have done my share of proof-reading C and C++ books. And there are a lot of errors. But that's not the worst of it. The worst books don't teach you anything, are full of errors, and the author continues to try to impress you with his work on the standards. The best books teach you and have a few errors that you will figure out on your own.
(I got into the proof-reading and writing biz years ago for a couple of years. How? By writing a letter about how book X was so full of mistakes it was unreadable. So I speak from experience)