C# Essentials, 2nd Edition 
By Brad Merrill, Peter Drayton, Ben Albahari


The unconfirmed error reports are from readers.  They have not yet been 
approved or disproved by the author or editor and represent solely the
opinion of the reader.

Here's a key to the markup:
        [page-number]: serious technical mistake
        {page-number}: minor technical mistake
        <page-number>: important language/formatting problem
        (page-number): language change or minor formatting problem
        ?page-number?: reader question or request for clarification

This page was updated January 21, 2003.


UNCONFIRMED  errors and comments from readers: 

[X]  last paragraph;
The book lists this URL as the sourse for the 'examples', the URL page identifies
that the book has many important 'examples', but the page referenced does not have
any access to the examples.


(4)  3rd paragraph (Interoperability with legacy code);
... which is a mechanism that enables C functions, structs, and callbacks to be
easily used from within in a .NET program.

Shouldn't this read "from within a .NET program" or "in a .NET program"? Not both...


(46)  First code example;
void Foo(int x);
viod Foo(double x); //oops void not viod


(78)  Table 2-4.;
There is no #end preprocessor directive.  However, there is #endregion preprocessor
directive.


{185}  System.Diagnostics entry;
The list of DLLs should include System.dll.

**** Safari ****
(section 1.4)
Describing how to compile and run a program the following
instructions are given in the second paragraph:

  "To compile this program into an executable, paste it into a text file,
  save it as Test.cs, then type csc Text.cs in the command prompt."

This should read "then type csc Test.cs" not Text.cs, since that is the
name we gave the file when we saved it.