Objective C # principle 50: Understanding ECMA standards)

Proactive C # principle 50: Understanding ECMA standards
Item 50: Learn About The ECMA Standard

The ECMA standard is an official description of all functions of the C # language. ECMA-334 defines C # Language 1.0 standards, and you can learn C #2.0's plan from the book the C # programming language ), this book is written by Anders hejlsberg, Scott wiltamuth, and Peter Golde (Addison-Wesley, 2003 ). This book is a language manual, not a guide. It details every function defined in the language in writing. Each language has only one flag, allowing you to better understand the functions of each language. When I am still writing this book, I often put it on my desk for reference.

If you are serious about C #ProgramPersonnel, you should understand the language, including the basic principles behind different functions. If you know when to apply every function during your work, it will make your work easier. You can better understand every detail hidden behind expressions in different languages.

For the content included in C #, you should thoroughly understand the common Runtime (CLR ). CLR and the common language infrastructure (CLI) standard are defined in the ECMA-335, which is also the CLR standard. As C #, This is the 1.0 standard. The common language infrastructure annotated standard, written by Ames Miller and Susann Ragsdale (Addison-Wesley, 2003), explains CLI version 2.0. This is a user manual that includes the public language subsystem (CLS). This will help to understand CLS compliance (Note: Only a few days ago I saw compliance translated as compliance on msdn, and I have always understood it as compatibility, of course, compatibility has other words, which are often understood .) . This also helps you understand the. NET runtime and basic ECMA standards.

C # the CLR Committee is still releasingCompositionFile, used to discuss the development of C # Language 2.0 and CLR. These discussions are of great value for understanding how C # will develop and change in the future.

In addition, a deep understanding of the current standards and increased intentions can help you create time-provenCode. By understanding the features that may be added to the language and environment, you can establish a favorable position when creating the software, and it can last longer. You may expect some modifications that may be made due to certain inevitable factors.

The software design is changing at any time, and C # will also develop and change. It is very likely that several versions will be developed on 2.0 in the future. This is a tool that you can use every day, at least most days. Learn more official instructions and always stand on the top of the content.

======================================
 

item 50: Learn About The ECMA Standard
The ECMA standard is the official word on how every feature in the C # Language behaves. ECMA-334 defines the 1.0 standard for the C # language. you can learn about the C #2.0 proposals from the book the C # programming language, by Anders hejlsberg, Scott wiltamuth, and Peter Golde (Addison-Wesley, 2003 ). this book is a language reference, not a tutorial. it explains in very pedantic detail exactly how each feature of the language works. each language feature is annotated so that you can better understand the justification of each language feature. while I was working on this book, I constantly had this reference open on my desk.

If you are a serious C # programmer, you shoshould understand the language, including the rationale behind different features. it will make your job easier if you know when to apply each feature in your own work. you will have a better understanding of any subtle differences in different language expressions.

In addition to the C # language, you shoshould understand the Common Language Runtime (CLR) thoroughly. the Clr and common language infrastructure (CLI) standards are defined in ECMA-335, the CLR standard. as with C #, this is version 1.0 of the standard. the common language infrastructure annotated standard, by James Miller and Susann Ragsdale (Addison-Wesley, 2003), explains the CLI version 2.0. this reference includes des the common language subsystem (CLS), which will help you understand the rules behind CLS compliance. this also helps you understand the ECMA standard for. net runtime and infrastructure.

Both the C # And CLR committees continue to publish working statements on the discussion and progress of the 2.0 version of the C # language and the CLR. the discussions are a valuable way to understand how C # will grow and change over time.

In addition, a deeper understanding of the current standard and the proposed enhancements will help you create code that stands the test of time. by understanding the features that will be added to the language and the environment, you are in a better position to create software that lasts longer into the future. you can anticipate the future modifications that might be necessary.

Software changes over time. C # will grow and change, probably for some time and for several revisions after 2.0. this is a tool that you use every day, for most of your day. learn the official definitions, and stay on top of them.