Errata

97 Things Every Programmer Should Know

Errata for 97 Things Every Programmer Should Know

Submit your own errata for this product.

The errata list is a list of errors and their corrections that were found after the product was released. If the error was corrected in a later version or reprint the date of the correction will be displayed in the column titled "Date Corrected".

The following errata were submitted by our customers and approved as valid errors by the author or editor.

Color key: Serious technical mistake Minor technical mistake Language or formatting error Typo Question Note Update

Version Location Description Submitted By Date submitted Date corrected
ePub, Safari Books Online
Page Preface
"Contact Us" Section

There is a link to companion content in the Preface that is no longer valid. Can this link be replaced or removed?

"The companion website for this book, where you can find all the contributions, contributor biographies, and more, is at:
programmer.97things.oreilly.com

Note from the Author or Editor:
Here is an updated link: http:// 97-things-every-x-should-know.gitbooks.io/97-things-every-programmer-should-know/content/en/

Anonymous  Dec 16, 2022  Jan 13, 2023
Printed
Page 91
command pipele low on page

"sort -r" should be "sort -rn" to get numerical sorting otherwise 2 will show up higher than 10.

Peter Allan  Sep 28, 2015  Jan 13, 2023
Printed
Page 137
First Bullet end of First Sentence

"disentangle them in the feature." should be "disentangle them in the future."

Note from the Author or Editor:
Yes, this is indeed a typo: "feature" needs to be changed to "future".

William Hartley  Feb 24, 2011  Jan 13, 2023
Printed, PDF
Page 183
Code in the middle of the page (after second text paragraph)

The following text

new SortedList<Customer)();

should be

new SortedList<Customer>();

In other words, the closing parenthesis immediately after "Customer" should be a closing angle bracket.

Kevlin Henney
 
Sep 17, 2010  Jan 13, 2023
Printed
Page 119
3rd line

"We have could captured" should read "We could have captured".

Robin Sibley  Apr 22, 2010  Jan 13, 2023