C# 3.0 in a Nutshell

Errata for C# 3.0 in a Nutshell

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.

The following errata were submitted by our customers and have not yet been approved or disproved by the author or editor. They solely represent the opinion of the customer.

Color Key: Serious Technical Mistake Minor Technical Mistake Language or formatting error Typo Question Note Update

Version Location Description Submitted By Date Submitted
Printed Page 1

Great book. I have about 20 nutshell books! I love them all. C# in a nutshell 3rd edition, has a smell of the ink/paper. Thank You.

David Einhorn  Jan 05, 2009 
Printed Page 9
Middle of page

static int InchesToFeet (int feet) {...} should read static int FeetToInches (int feet) {...}

Printed Page 32
Multidimensional Arrays

Two kinds of multidimensional arrays are described: rectangular and jagged. This differs from the C# reference, where only the "rectangular" arrays are considered multidimensional. I marked this as a serious technical mistake because it can be a source of substantial confusion if you then refer to the .NET documentation. For example, the .NET documentation on Array.Copy describes how it handles multidimensional arrays, and Array.CopyTo is said to work only with single dimensional arrays. Here, however, multidimensional means "multidimensional rectangular array", in your vocabulary, and "single dimensional" includes jagged arrays! I do see that the book's coverage of Array.Copy and Array.CopyTo carefully refers to a "multidimensional rectangular array" (p. 247). So, at least the book internally consistent. Nonetheless, I still think it would be far better to prevent confusion and follow the terminology that Microsoft uses.

Kevin Braun  Jan 28, 2009 
Printed Page 92
bottom of page

The boolian variable "horizontal" would be better labeled "vertical"! Left and Right edges are vertical, not horizontal!

Mark Owen  Jul 06, 2009 
Printed Page 110
line 5

The book uses the term "listener" without defining it earlier in the text, or having a reference in the index. In fact, I think the authors mean "subscriber" anyway.

Mark Owen  Jul 13, 2009 
Printed Page 112
near the bottom of the page

In the code of class Stock: the type of delegate should PriceChanged Handler, not PriceChanged : ... public event PriceChanged PriceChanged; ...

Peyman  Jun 28, 2010 
Printed Page 112
Events, 3rd paragraph

A subscriber decides when to start and stop listening, by calling +- and -= should read "+= and -="

Guy Davis  Jul 17, 2010 
Printed Page 112
Example at bottom, continues to page 113

The example declares public delegate void PriceChangedHandler( decimal oldPrice, decimal newPrice ); but in the class that's supposed to be using this type it doesn't use the same type name: public class Stock { ... public event PriceChanged PriceChanged; <--- error it should say: public event PriceChangedHandler PriceChanged;

Joe Binter  Dec 02, 2011 
PDF Page 200
Table 6-2. Standard numeric format strings

Letter N, 2nd sample input, the format string should be "N2" not "F2"

Gerhard Fries  Oct 27, 2010 
PDF Page 201
Table 6-3. Custom numeric format strings

Specifier ",", Meaning "Multiplier", 2nd sample input, the trailing quotation marks are missing.

Gerhard Fries  Oct 27, 2010 
Printed Page 275
Linq complete example at bottom of page

using System.Collections.Generic; is missing in the example (for IEnumerable).

Anonymous  Jun 08, 2010 
Printed Page 314
middle of the page

The sentence: "...assigning the Purchase.Customer property would automatically add the new customer to the Customer.Purchases entity set..." should read: "...assigning the Purchase.Customer property would automatically add the new purchase to the Customer.Purchases entity set..."

Anonymous  Jun 28, 2010 
Printed Page 564
9th line

Page 564, 9th line Change: Console.WriteLine(t); To: Console.WriteLine(t.FullName);