Effective C # Principle 50: Understanding ECMA Standards

The ECMA Standard is an official description of all the features of the C # language. ECMA-334 defines the C # language 1.0 standard, you can learn c#2.0 's plan from the C # programming language book (now is not a plan), the author of this book is Anders Hejlsberg, Scott Wiltamuth, and Peter Golde (Addison-wesley, 2003). This book is a language handbook, not a guide. It details every function of the written definition of this language. Each language is just a marker that allows you to understand the function of each language better. When I was still writing this book, I often put the book on my desk for reference.

If you are serious about C # programmers, you should understand this language, including the basics behind different functions. If you are working, you know when to apply every feature, it will make your job easier. You can better understand each of the different details that are hidden behind different language expressions.

For the incidental content of C #, you should thoroughly understand the common runtime (CLR). The CLR and the common language Base (CLI) standards are defined in ECMA-335, which is also the CLR standard. As C #, this is still the standard of 1.0. Common language base tag standard this book (the Common Language Infrastructure Annotated Standard), by Ames Miller and Susann Ragsdale (Addison-wesley, 2003 ), explains the 2.0 version of the CLI. This is a manual that includes the common language subsystem (CLS), which helps to understand CLS compliance (the last few days saw compliance translated as compliance on MSDN, and I've always understood compatibility, and of course there are other words for compatibility, and many times it's a question of understanding.) ) behind the principle. This will also help you understand. NET runtime and base ECMA standards.

C # and the CLR committee are also publishing working documents to discuss the development of the 2.0 version of the C # language and the CLR. These discussions are valuable for understanding how C # will evolve and change in the future.

On the other hand, a deep understanding of current standards and increased intent can help you create code that will withstand time considerations. By understanding these features that may be added to the language and to the environment, you can be in a good position to create the software, and it can last longer. You can anticipate some of the changes that may be made by some necessary factors.

Software design changes at any time, C # will also develop and change, it is likely that the time will be in 2.0 to develop several versions. This is a tool that you can use every day, at least for most of the day. Learn more about the official notes and always stand on top of the content.

Back to the Tutorial directory