Errata for C# 3.0 in a Nutshell

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

The figure does not match the code, either of code or figure should be change. The code reads p1.X =9 and p2.X=7 and remains unchanged, but in the figure we see that p1.X=7 and p2.X=9.

Note from the Author or Editor:
Figure 2-2 should be changed so that the numbers 7 and 9 are swapped around.

The page now ends with "for example:" followed by no example. Here are the 6 lines that should follow: class BaseClass { protected virtual void Foo() {} } class Subclass1 : BaseClass { protected override void Foo() {} } // OK class Subclass2 : BaseClass { public override void Foo() {} } // Error The compiler prevents any inconsistent use of access modifiers. For example, a subclass itself can be less accessible than a base class, but not more accessible: internal class A {} public class B : A {} // Error

{95} 4th line, change Console.WriteLine (typeof(BorderSide), Enum.IsDefined (side)); //False to Console.WriteLine (Enum.IsDefined (typeof(BorderSide), side)); //False

In the example: static void Swap<T> (ref T a, ref T b) { T temp = b; //SHOULD BE EITHER T temp = a; a = b; // OR b = a; b = temp; }

Note from the Author or Editor:
Method should be: static void Swap<T> (ref T a, ref T b) { T temp = a; a = b; b = temp; }

I believe this code example should include at the end the line: enumerator.Dispose(); If this code is (as it states) intended to be functionally the same as a foreach statement shown above.

Note from the Author or Editor:
This has been fixed in the 4th edition.

if (Zoo != null) Zoo.NotifyNameChange(this, value); should bee: if (Zoo != null) Zoo.Animals.NotifyNameChange(this, value);

There's an error in Figure 8-2 on page 283 - which is also reproduced on the back cover. There's an extra line betweeen the select and group-clause boxes which shouldn't be present. Here's how it should look: http://www.albahari.com/nutshell/linqsyntax.aspx

The descriptions for the methods 'TakeWhile' and 'SkipWhile' both state [Emits|Ignores] elements from the input sequence until the predicate is true This is incorrect, they operate while the predicate is true, and operate until the predicate is false. From MSDN on TakeWhile: http://msdn.microsoft.com/en-us/library/bb534804.aspx "Returns elements from a sequence as long as a specified condition is true." The examples on page 327 also make the operation clear. The problem is that the operations continue WHILE the predicate is true, rather than UNTIL. To use until, you would have to state they continue until false, which is awkward. They should be reworded, as their function name suggests, to say they perform their action WHILE the predicate is true.

Note from the Author or Editor:
Table, half way down page 324: - In the middle column ("Description") of TakeWhile, change "until" to "while" so that it reads "Emits elements from the input sequence while the predicate is true" - In the middle column ("Description") of SkipWhile, change "until" to "while" so that it reads "Ignores elements from the input sequence while the predicate is true, and then emits the rest" Similarly, half way down page 327, change "until" to "while" in the first and second sentences under section "TakeWhile and "SkipWhile".

writer.WriteStartElement (

Note from the Author or Editor:
Page 406, first code listing, third line. Change "firstname" to "lastname", so that it reads: writer.WriteStartElement ("o", "customer", "http://oreilly.com"); writer.WriteElementString ("o", "firstname", "http://oreilly.com", "Jim"); writer.WriteElementString ("o", "lastname", "http://oreilly.com", "Bo"); writer.WriteEndElement();

In the sentence, "The client instantiates a NamedClientStream and then calls Connect (with an optional timeout)", "NamedClientStream" should say "NamedPipeClientStream".

"in other words, reads until IsMessageComplete is false:" should be "in other words, reads until IsMessageComplete is true:". In the example given, the do-while loop exits when (!s.IsMessageComplete ) is false. VS' Object Browser tells me: public bool IsMessageComplete {get;} IsMessageComplete Returns: true if there are no more characters to read in the message; otherwise, false.

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

the output of Console.WriteLine(t.FullName) should be: // System.Environment+SpecialFolder instead of: // System.Environment+StringBuilder

Page 587, Passing Arguments to a Dynamic Method section, 4th line Change: when calling DefineMethod. to: when calling DynamicMethod constructor.

Note from the Author or Editor:
Change: when calling DefineMethod. to: when calling DynamicMethod's constructor.

Page 587, Passing Arguments to a Dynamic Method section, 4th line Change: when calling DefineMethod. to: when calling DynamicMethod constructor.

Note from the Author or Editor:
Change: ...when calling DefineMethod. to: ...when constructing the DynamicMethod.

Page 600, Attaching Attributes section, 5th-to-last line Change: new object[] { "FirstName", 3 } // Property values To: new object[] { "http://test/", 3 } // Property values

Page 600, Attaching Attributes section, 5th-to-last line Change: new object[] { "FirstName", 3 } // Property values To: new object[] { "http://test/", 3 } // Property values

Note from the Author or Editor:
Good spot.

Page 601, second code snippet, 2nd-to-last line Change: gen.Emit(OpCodes.Ldarg_1); To: gen.Emit(OpCodes.Ldarg_0);

Page 601, second code snippet, 2nd-to-last line Change: gen.Emit(OpCodes.Ldarg_1); To: gen.Emit(OpCodes.Ldarg_0);

Note from the Author or Editor:
The line to change is about 2/3 way down the page. It should read: gen.Emit (OpCodes.Ldarg_0); And to whoever reported this, well-spotted!