Errata

C# 6.0 Pocket Reference

Errata for C# 6.0 Pocket Reference

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
Everywhere

Shouldn't the 'volatile' keyword be documented? I didn't see it in the text, and it's not in the index.

Jeremy Kelly  Jun 04, 2016 
Printed Page 3
First sentence after heading "Using Code Examples"

The sentence states: "The programs and code snippets in this book is available are all available as interactive samples in LINQPad..."

Remove "is available "

David Sieber  Aug 30, 2018 
Printed Page 22
2nd paragraph

"Integral literals can use decimal or hexadecimal notation; hexadecimal is denoted with 0x prefix (e.g., 0x7f is equivalent to 127). Real literals may use decimal or exponential notation such as 1E06."

It seems to me that the first word ("Integral") in this paragraph must be a typo and should read "Integer". "Integral literals" would encompass more than numeric types therefore the sentence doesn't make sense as it is currently written. When considered with the subsequent sentence quoted above, which goes on to explain the other numeric type "Real", it is even more apparent that "Integer" was the intention of the authors.

Colin Hughes  Sep 08, 2017 
Printed Page 103
1st coded snippet

int[] data;

should be:

int[] data = new int[100];

Patrick Fischer  Mar 27, 2017 
Printed Page 194
Last code example

The closing curly brace is missing from the lambda expression.

Jeremy Kelly  Jun 04, 2016 
Printed Page 214
middle of left column

">= (less-than operator), 29"
is incorrect and should be removed because both >= and < have already been correctly indexed.

Anonymous  Jan 29, 2016