InfoQ Homepage News Review: C# Annotated Standard

Review: C# Annotated Standard


When Microsoft, along with HP and Intel, offered the C# Standard to ECMA in 2000, it was a major break in tradition. Up until that point, all programming languages developed by Microsoft were controlled solely in-house. While documentation was certainly provided, the general populace never got the in-depth to really explore the nooks and crannies of the language, let alone write their own compiler.

An unfortunate side effect of being a standard is that it is written like one. Often the standard will say a compiler may do something but is not required to. While this is fine at a conceptual level, it makes it harder than necessary to what the Microsoft C# compiler actually does.

This where the book by Jagger, Perry, and Sestoft comes into play. They take the C# 2.0 standard and fill in the blanks. This book is full of detailed information on how the Microsoft choose to implement its C# compiler. And though possibly dated, it also includes the same information on Mono's C# compiler.

The real value of this book comes from its discussion of edge cases. For example, the standard includes a section on the FGAB problem. Specifically if F(G<A, B>(7)) should be interpreted as F having the arguments G<A, B> and 7 or the arguments (G<A) and (B>7). While not much of an issue in C# 2, this far more important now that passing functions to other functions is becoming common. The authors build on the standard both by clarifying the rather esoteric text and by describing how the compilers actually handle it. (Both Microsoft and Mono simply fail to parse it in this case.)

If any complaints are to be made about this book, it is that it tends to be very dry and technical. While they do include a lot of background information about how the language came to be, it never quite gets to the conversational level we find in Framework Design Guidelines.

Annotated C# Standard by Jon Jagger, Nigel Perry, and Peter Sestoft is currently in print and also available via Google Book Search.

We need your feedback

How might we improve InfoQ for you

Thank you for being an InfoQ reader.

Each year, we seek feedback from our readers to help us improve InfoQ. Would you mind spending 2 minutes to share your feedback in our short survey? Your feedback will directly help us continually evolve how we support you.

Take the Survey

Rate this Article


Hello stranger!

You need to Register an InfoQ account or or login to post comments. But there's so much more behind being registered.

Get the most out of the InfoQ experience.

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p

Community comments

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p


Is your profile up-to-date? Please take a moment to review and update.

Note: If updating/changing your email, a validation request will be sent

Company name:
Company role:
Company size:
You will be sent an email to validate the new email address. This pop-up will close itself in a few moments.