DOCSLIB.ORG

Common Language Infrastructure (CLI) Partitions I to IV

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Common Language Infrastructure (CLI) Partitions I to IV Standard ECMA-335 December 2001 Standardizing Information and Communication Systems Common Language Infrastructure (CLI) Partitions I to IV Phone: +41 22 849.60.00 - Fax: +41 22 849.60.01 - URL: http://www.ecma.ch - Internet: [email protected] Standard ECMA-335 December 2001 Standardizing Information and Communication Systems Common Language Infrastructure (CLI) Partitions I to IV Partition I : Concepts and Architecture Partition II : Metadata Definition and Semantics Partition III : CLI Instruction Set Partition IV : Profiles and Libraries Phone: +41 22 849.60.00 - Fax: +41 22 849.60.01 - URL: http://www.ecma.ch - Internet: [email protected] mb - Ecma-335-Part-I-IV.doc - 16.01.2002 16:02 Common Language Infrastructure (CLI) Partition I: Concepts and Architecture - i - Table of Contents 1Scope 1 2 Conformance 2 3 References 3 4 Glossary 4 5 Overview of the Common Language Infrastructure 19 5.1 Relationship to Type Safety 19 5.2 Relationship to Managed Metadata-driven Execution 20 5.2.1 Managed Code 20 5.2.2 Managed Data 21 5.2.3 Summary 21 6 Common Language Specification (CLS) 22 6.1 Introduction 22 6.2 Views of CLS Compliance 22 6.2.1 CLS Framework 22 6.2.2 CLS Consumer 22 6.2.3 CLS Extender 23 6.3 CLS Compliance 23 6.3.1 Marking Items as CLS-Compliant 24 7 Common Type System 25 7.1 Relationship to Object-Oriented Programming 27 7.2 Values and Types 27 7.2.1 Value Types and Reference Types 27 7.2.2 Built-in Types 27 7.2.3 Classes, Interfaces and Objects 28 7.2.4 Boxing and Unboxing of Values 29 7.2.5 Identity and Equality of Values 29 7.3 Locations 30 7.3.1 Assignment Compatible Locations 30 7.3.2 Coercion 30 7.3.3 Casting 31 7.4 Type Members 31 - ii - 7.4.1 Fields, Array Elements, and Values 31 7.4.2 Methods 31 7.4.3 Static Fields and Static Methods 32 7.4.4 Virtual Methods 32 7.5 Naming 32 7.5.1 Valid Names 32 7.5.2 Assemblies and Scoping 33 7.5.3 Visibility, Accessibility, and Security 34 7.6 Contracts 36 7.6.1 Signatures 37 7.7 Assignment Compatibility 40 7.8 Type Safety and Verification 40 7.9 Type Definers 40 7.9.1 Array Types 41 7.9.2 Unmanaged Pointer Types 43 7.9.3 Delegates 43 7.9.4 Interface Type Definition 43 7.9.5 Class Type Definition 44 7.9.6 Object Type Definitions 46 7.9.7 Value Type Definition 48 7.9.8 Type Inheritance 49 7.9.9 Object Type Inheritance 49 7.9.10 Value Type Inheritance 49 7.9.11 Interface Type Inheritance 49 7.10 Member Inheritance 50 7.10.1 Field Inheritance 50 7.10.2 Method Inheritance 50 7.10.3 Property and Event Inheritance 50 7.10.4 Hiding, Overriding, and Layout 50 7.11 Member Definitions 51 7.11.1 Method Definitions 52 7.11.2 Field Definitions 52 7.11.3 Property Definitions 52 7.11.4 Event Definitions 53 7.11.5 Nested Type Definitions 54 8 CLI Metadata 55 8.1 Components and Assemblies 55 - iii - 8.2 Accessing Metadata 55 8.2.1 Metadata Tokens 55 8.2.2 Member Signatures in Metadata 56 8.3 Unmanaged Code 56 8.4 Method Implementation Metadata 56 8.5 Class Layout 56 8.6 Assemblies: Name Scopes for Types 57 8.7 Metadata Extensibility 58 8.8 Globals, Imports, and Exports 59 8.9 Scoped Statics 59 9 Name and Type Rules for the Common Language Specification 60 9.1 Identifiers 60 9.2 Overloading 60 9.3 Operator Overloading 61 9.3.1 Unary Operators 61 9.3.2 Binary Operators 62 9.3.3 Conversion Operators 63 9.4 Naming Patterns 63 9.5 Exceptions 64 9.6 Custom Attributes 64 10 Collected CLS Rules 66 11 Virtual Execution System 69 11.1 Supported Data Types 69 11.1.1 Native Size: native int, native unsigned int, O and & 70 11.1.2 Handling of Short Integer Data Types 71 11.1.3 Handling of Floating Point Datatypes 71 11.1.4 CIL Instructions and Numeric Types 74 11.1.5 CIL Instructions and Pointer Types 75 11.1.6 Aggregate Data 76 11.2 Module Information 79 11.3 Machine State 79 11.3.1 The Global State 79 11.3.2 Method State 80 11.4 Control Flow 83 11.4.1 Method Calls 84 11.4.2 Exception Handling 87 - iv - 11.5 Proxies and Remoting 92 11.6 Memory Model and Optimizations 92 11.6.1 The Memory Store 92 11.6.2 Alignment 92 11.6.3 Byte Ordering 93 11.6.4 Optimization 93 11.6.5 Locks and Threads 93 11.6.6 Atomic Reads and Writes 94 11.6.7 Volatile Reads and Writes 94 11.6.8 Other Memory Model Issues 94 11.7 Atomicity of Memory Accesses 95 12 Index 97 1 1Scope 2 This ECMA Standard defines the Common Language Infrastructure (CLI) in which applications written in 3 multiple high level languages may be executed in different system environments without the need to rewrite the 4 application to take into consideration the unique characteristics of those environments. This ECMA Standard 5 consists of several sections in order to facilitate understanding various components by describing those 6 components in their separate sections. These sections are: 7 Partition I: Architecture 8 Partition II: Metadata Definition and Semantics 9 Partition III: CIL Instruction Set 10 Partition IV: Profiles and Libraries 11 Partition V: Annexes - 2 - 1 2Conformance 2 A system claiming conformance to this ECMA Standard shall implement all the mandatory requirements of 3 this standard, and shall specify the profile (see Partition IV) that it implements. The minimal implementation is 4 the Kernel Profile (see Partition IV). A conforming implementation may also include additional functionality 5 that does not prevent running code written to rely solely on the profile as specified in this standard. For 6 example, it may provide additional classes, new methods on existing classes, or a new interface on a 7 standardized class, but it shall not add methods or properties to interfaces specified in this standard. 8 A compiler that generates Common Intermediate Language (CIL, see Partition III) and claims conformance to 9 this ECMA Standard shall produce output files in the format specified in this standard and the CIL it generates 10 shall be valid CIL as specified in this standard. Such a compiler may also claim that it generates verifiable 11 code, in which case the CIL it generates shall be verifiable as specified in this standard. - 3 - 1 3 References 2 IEC 60559:1989, Binary Floating-point Arithmetic for Microprocessor Systems (previously designated IEC 3 559:1989) 4 ISO/IEC 10646 (all parts), Information technology — Universal Multiple-Octet Coded Character Set (UCS). 5 The Unicode Consortium. The Unicode Standard, Version 3.0, defined by: The Unicode Standard, Version 3.0 6 (Reading, MA, Addison-Wesley, 2000. ISBN 0-201-61633-5), and Unicode Technical Report #15: Unicode 7 Normalization Forms. 8 ISO/IEC 646:1991 Information technology -- ISO 7-bit coded character set for information interchange 9 ISO/IEC 11578:1996 (E) Information technology - Open Systems Interconnection - Remote Procedure Call 10 (RPC), Annex A: Universal Unique Identifier 11 Federal Information Processing Standard (FIPS 180-1), Secure Hash Standard (SHA-1), 1995 April 7. 12 Extensible Markup Language (XML) 1.0 (Second Edition), 2000 October 6, http://www.w3.org/TR/2000/REC- 13 xml-20001006 14 Network Working Group. RFC 2616: Hypertext Transfer Protocol -- HTTP/1.1. R. Fielding, J. Gettys, J. 15 Mogul, H. Frystyk, L. Masinter, P. Leach, T. Berners-Lee. 1999 June, ftp://ftp.isi.edu/in-notes/rfc2616.txt 16 Network Working Group. RFC 2617: HTTP Authentication: Basic and Digest Access Authentication. J. 17 Franks, P. Hallam-Baker, J. Hostetler, S. Lawrence, P. Leach, A. Luotonen, L. Stewart. 1999 June, 18 ftp://ftp.isi.edu/in-notes/rfc2617.txt 19 IETF (Internet Engineering Task Force). RFC 2396: Uniform Resource Identifiers (URI): Generic Syntax. T. 20 Berners-Lee, R. Fielding, L. Masinter. 1998 August, http://www.ietf.org/rfc/rfc2396.txt. 21 Network Working Group. RFC-1222: Advancing the NSFNET Routing Architecture. H-W Braun, Y. Rekhter. 22 1991 May, ftp://ftp.isi.edu/in-notes/rfc1222.txt -4- 1 4Glossary 2 For the purpose of this ECMA Standard, the following definitions apply. They are collected here for ease of 3 reference, but the definition is presented in context elsewhere in the specification, as noted. Definitions 4 enclosed in square brackets [ ] were not extracted from the body of the standard. 5 The remainder of this section and its subsections contain only informative text Term Description Pt Ch Section Abstract Only an abstract object type is allowed to define method I 7.9.6.2 Concreteness contracts for which the type or the VES does not also provide the implementation. Such method contracts are called abstract methods Accessibility A type scopes all of its members, and it also specifies I 7.5.3.2 Accessibility of of members the accessibility rules for its members. Except where Members noted, accessibility is decided based only on the statically visible type of the member being referenced and the type and assembly that is making the reference. The CTS supports seven different rules for accessibility: Compiler-Controlled; Private; Family; Assembly; Family-and-Assembly; Family-or-Assembly; Public.
Load more

Recommended publications
  • Non-Invasive Software Transactional Memory on Top of the Common Language Runtime
    University of Neuchâtel Computer Science Department (IIUN) Master of Science in Computer Science Non-Invasive Software Transactional Memory on top of the Common Language Runtime Florian George Supervised by Prof. Pascal Felber Assisted by Patrick Marlier August 16, 2010 This page is intentionally left blank Table of contents 1 Abstract ................................................................................................................................................. 3 2 Introduction ........................................................................................................................................ 4 3 State of the art .................................................................................................................................... 6 4 The Common Language Infrastructure .................................................................................. 7 4.1 Overview of the Common Language Infrastructure ................................... 8 4.2 Common Language Runtime.................................................................................. 9 4.3 Virtual Execution System ........................................................................................ 9 4.4 Common Type System ........................................................................................... 10 4.5 Common Intermediate Language ..................................................................... 12 4.6 Common Language Specification.....................................................................
    [Show full text]
  • Programming with Windows Forms
    A P P E N D I X A ■ ■ ■ Programming with Windows Forms Since the release of the .NET platform (circa 2001), the base class libraries have included a particular API named Windows Forms, represented primarily by the System.Windows.Forms.dll assembly. The Windows Forms toolkit provides the types necessary to build desktop graphical user interfaces (GUIs), create custom controls, manage resources (e.g., string tables and icons), and perform other desktop- centric programming tasks. In addition, a separate API named GDI+ (represented by the System.Drawing.dll assembly) provides additional types that allow programmers to generate 2D graphics, interact with networked printers, and manipulate image data. The Windows Forms (and GDI+) APIs remain alive and well within the .NET 4.0 platform, and they will exist within the base class library for quite some time (arguably forever). However, Microsoft has shipped a brand new GUI toolkit called Windows Presentation Foundation (WPF) since the release of .NET 3.0. As you saw in Chapters 27-31, WPF provides a massive amount of horsepower that you can use to build bleeding-edge user interfaces, and it has become the preferred desktop API for today’s .NET graphical user interfaces. The point of this appendix, however, is to provide a tour of the traditional Windows Forms API. One reason it is helpful to understand the original programming model: you can find many existing Windows Forms applications out there that will need to be maintained for some time to come. Also, many desktop GUIs simply might not require the horsepower offered by WPF.
    [Show full text]
  • NET Core 3 and Unit Testing
    Learn C# Programming A guide to building a solid foundation in C# language for writing efcient programs Marius Bancila Rafaele Rialdi Ankit Sharma BIRMINGHAM—MUMBAI Learn C# Programming Copyright © 2020 Packt Publishing All rights reserved. No part of this book may be reproduced, stored in a retrieval system, or transmitted in any form or by any means, without the prior written permission of the publisher, except in the case of brief quotations embedded in critical articles or reviews. Every efort has been made in the preparation of this book to ensure the accuracy of the information presented. However, the information contained in this book is sold without warranty, either express or implied. Neither the authors, nor Packt Publishing or its dealers and distributors, will be held liable for any damages caused or alleged to have been caused directly or indirectly by this book. Packt Publishing has endeavored to provide trademark information about all of the companies and products mentioned in this book by the appropriate use of capitals. However, Packt Publishing cannot guarantee the accuracy of this information. Commissioning Editor: Richa Tripathi Acquisition Editor: Alok Dhuri Senior Editor: Storm Mann Content Development Editor: Ruvika Rao Technical Editor: Pradeep Sahu Copy Editor: Safs Editing Language Support Editor: Safs Editing Project Coordinator: Francy Puthiry Proofreader: Safs Editing Indexer: Pratik Shirodkar Production Designer: Jyoti Chauhan First published: April 2020 Production reference: 1280420 Published by Packt Publishing Ltd. Livery Place 35 Livery Street Birmingham B3 2PB, UK. ISBN 978-1-78980-586-4 www.packt.com To my smart boys, Cristian and Bogdan, who love learning new things every day.
    [Show full text]
  • PV178: Programming for .NET Framework Introduction to .NET and C
    Introduction to .NET Framework Introduction to C# References PV178: Programming for .NET Framework Introduction to .NET and C# VojtˇechForejt, forejt@fi.muni.cz Martin Osovsk´y,[email protected] Faculty of Informatics and Institute of Computer Science Masaryk University March 14, 2010 Introduction to .NET Framework Introduction to C# References Overveiw Microsoft.Net Technology Suite standards (CLI) and their implementations (CLR) programming languages (C# among others) development tools (Microsoft Visual Studio, Microsoft .Net Framework SDK) runtime (Microsoft .Net Framework) application toolkits (ASP.Net, ADO.Net,. ) Introduction to .NET Framework Introduction to C# References CLI Overview Common Language Infrastructure international standard (ECMA #335, ISO/IEC 23271:2003), see [7] a standard base for creating execution and development environments interoperability { languages and libraries conforming to the standard should work together seamlessly Introduction to .NET Framework Introduction to C# References CLI Overview CLI Components CLI itself defines the Common Type System (CTS) the Common Language Specification (CLS) metadata (description of the code units, such as visibility, security requirements, etc.) portable and platform-agnostic file format for managed code common Intermediate Language (CIL) instruction set basic requirements on the Virtual Execution System a programming framework (a class library) Introduction to .NET Framework Introduction to C# References Common Type System CTS: the Common Type System The Complete set of types available to a CLI-compliant language based both on representation of values and their behaviour designed for language interoperability designed via set of rules { types are extensible (by derivation), type system is not designed for broad coverage: object-oriented, procedural and functional languages (C#, JScript, C++, F#, COBOL, J#, etc.
    [Show full text]
  • NET Framework Overview
    .NET Framework Overview .NET Framework, CLR, MSIL, Assemblies, CTS, etc. Svetlin Nakov Telerik Corporation www.telerik.com Table of Contents 1. What is .NET? Microsoft .NET platform architecture 2. What is .NET Framework? .NET Framework Architecture 3. Common Language Runtime (CLR) 4. Managed Code 5. Intermediate Language MSIL 6. Assemblies and Metadata 7. .NET Applications Table of Contents (2) 8. Common Language Infrastructure (CLI) and integration of different languages Common Language Specification (CLS) Common Type System (CTS) 9. Framework Class Library 10. Integrated Development Environment Visual Studio .NET Framework Microsoft's Platform for Application Development What is the .NET Platform? The .NET platform Microsoft's platform for software development Unified technology for development of almost any kind of applications GUI / Web / RIA / mobile / server / cloud / etc. .NET platform versions .NET Framework Silverlight / Windows Phone 7 .NET Compact Framework What is .NET Framework? .NET Framework An environment for developing and executing .NET applications Unified programming model, set of languages, class libraries, infrastructure, components and tools for application development Environment for controlled execution of managed code It is commonly assumed that .NET platform == .NET Framework .NET Framework Components Common Language Runtime (CLR) Environment for controlled execution of programmed code – like a virtual machine Executes .NET applications Framework Class Library (FCL) Standard class library
    [Show full text]
  • C# Essentials
    C# Essentials C# 4.0 Essentials 2 C# Essentials C# 4.0 Essentials – Version 1.04 © 2010 Payload Media. This eBook is provided for personal use only. Unauthorized use, reproduction and/or distribution strictly prohibited. All rights reserved. The content of this book is provided for informational purposes only. Neither the publisher nor the author offers any warranties or representation, express or implied, with regard to the accuracy of information contained in this book, nor do they accept any liability for any loss or damage arising from any errors or omissions. Find more technology eBooks at www.ebookfrenzy.com 3 C# Essentials Table of Contents Chapter 1. About C# Essentials ................................................................................................. 12 Chapter 2. The C# Language and Environment ........................................................................ 13 2.1 A Brief History of Computer Programming Languages .................................................. 13 2.2 What exactly is C#? ........................................................................................................ 14 2.3 The Common Language Infrastructure (CLI) .................................................................. 14 2.4 Common Intermediate Language (CIL) .......................................................................... 15 2.5 Virtual Execution System (VES) ...................................................................................... 15 2.6 Common Type System (CTS) & Common Language Specification
    [Show full text]
  • Porting the .NET Compact Framework to Symbian Phones
    JOURNAL OF OBJECT TECHNOLOGY Online at http://www.jot.fm. Published by ETH Zurich, Chair of Software Engineering ©JOT, 2006 Vol. 5, No. 3, Special issue: .NET Technologies 2005 Conference, 2006 Porting the .NET Compact Framework to Symbian Phones Frank Siegemund, Robert Sugar, Alain Gefflaut and Friedrich van Megen, European Microsoft Innovation Center Abstract This paper presents our experiences in porting selected parts of the .NET Compact Framework to Symbian smartphones. Our port includes support for basic services such as threading and file access, low-level networking modules as well as Web Services. We also present a portable .NET GUI for the Symbian platform. The paper shows how the programming models of .NET can be efficiently mapped to the runtime structures provided by operating systems for resource-constrained devices such as the Symbian OS. In a detailed analysis, we compare the performance of our port to that of Java and native code. 1 INTRODUCTION During the last two decades, mobile phones have become almost ubiquitous. As a result of this development, it is increasingly important for companies to offer applications for mobile users that seamlessly interoperate with server-based business software in order to improve customer satisfaction and service availability. The .NET Framework has been a popular platform for creating such applications and services both on stationary computers and Windows CE-based mobile devices. While Windows CE-based smartphones are getting increasing attention, however, a number of phones are currently based on the Symbian operating system. According to a recent study by Canalys [Canalys], the Symbian OS owned 63.2 % of the mobile device OS market at the end of the third quarter 2005.
    [Show full text]
  • Penn P. Wu, Phd. 1 Lecture #1 Introducing Visual C# Introduction
    Lecture #1 Introducing Visual C# Introduction to According to Microsoft, C# (pronounced “C sharp”) is a programming language that is the C# designed for building a variety of applications that run on the .NET Framework. C# is simple, Language and powerful, type-safe, and object-oriented. It provides many innovations to enable rapid the .NET application development while retaining the expressiveness and elegance of C-style languages. Framework C# was developed around 2000 by Microsoft within its .NET initiative and later approved as a standard by Ecma and ISO. Microsoft’s Visual Studio supports Visual C# with a full-featured code editor, compiler, project templates, designers, code wizards, a powerful and easy-to-use debugger, and other tools. C# programs run on the .NET Framework, which is an integral component of Windows that includes a virtual execution system called the common language runtime (CLR) and a unified set of class libraries. The CLR is Microsoft’s implementation of the common language infrastructure (CLI). It is an international standard that is the basis for creating execution and development environments in which languages and libraries work together seamlessly. Visual Studio Visual Studio 2017 is a rich, integrated development environment (IDE) for creating stunning 2017 and the applications for Windows, Android, and iOS, as well as modern web applications and cloud Developer services. It is a full-featured and extensible toolkit for developers to build Windows-based Command applications. As of January 2019, Microsoft says “Visual Studio Community is free for Prompt individual developers, open source projects, academic research, training, education, and small professional teams”.
    [Show full text]
  • Common Language Runtime: a New Virtual Machine
    Common Language Runtime: a new virtual machine João Augusto Martins Ferreira Departamento de Informática – Universidade do Minho 4710-057, Portugal [email protected] Abstract. Virtual Machines provide a runtime execution platform combining bytecode portability with a performance close to native code. An overview of current approaches precedes an insight into Microsoft CLR (Common Language Runtime), comparing it to Sun JVM (Java Virtual Machine) and to a native execution environment (IA 32). A reference is also made to CLR in a Unix platform and to techniques on how CLR improves code execution. 1 Introduction Virtual machines, intermediate languages and language independent execution platforms are not a recent technology and we heard talking about it . Backing in time we see UNCOL1, USCD P-code2, ANDF3, AS-400, some hardware emulators like VMWare or Transmeta Crusoe, binary translation [2], the JVM [3] and more recently the Microsoft implementation of Common Language Infrastructure (CLI) [4]. The word “virtual” is used because, generally, it is a technology that is implemented in software on top of a "real" hardware platform and operating system. All virtual machines have a programming language (or more) that is compiled and will only run on that virtual platform. The virtual machine plays a central role because it provides a layer of abstraction between a compiled program and the underlying hardware platform and operating system. So, this is great for portability because any program that targets the virtual machine will run, whatever maybe underneath a particular virtual machine implementation. This is great comparing to native compilers and execution. For instance, runtime code generation for C must take into account the machine architecture, operating system conventions and compiler-specific issues such as calling conventions [5].
    [Show full text]
  • PV178: Programming for .NET Framework Introduction to .NET and C
    Introduction to .NET Framework Introduction to C# References PV178: Programming for .NET Framework Introduction to .NET and C# VojtˇechForejt, forejt@fi.muni.cz Martin Osovsk´y,[email protected] Faculty of Informatics and Institute of Computer Science Masaryk University February 19, 2009 Introduction to .NET Framework Introduction to C# References Overveiw Microsoft.Net Technology Suite standards (CLI) and their implementations (CLR) programming languages (C# among others) development tools (Microsoft Visual Studio, Microsoft .Net Framework SDK) runtime (Microsoft .Net Framework) application toolkits (ASP.Net, ADO.Net,. ) Introduction to .NET Framework Introduction to C# References CLI Overview Common Language Infrastructure international standard (ECMA #335, ISO/IEC 23271:2003), see [7] a standard base for creating execution and development environments interoperability { languages and libraries conforming to the standard should work together seamlessly Introduction to .NET Framework Introduction to C# References CLI Overview CLI Components CLI itself defines the Common Type System (CTS) the Common Language Specification (CLS) metadata (description of the code units, such as visibility, security requirements, etc.) portable and platform-agnostic file format for managed code common Intermediate Language (CIL) instruction set basic requirements on the Virtual Execution System a programming framework (a class library) Introduction to .NET Framework Introduction to C# References Common Type System CTS: the Common Type System The Complete set of types available to a CLI-compliant language based both on representation of values and their behaviour designed for language interoperability designed via set of rules { types are extensible (by derivation), type system is not designed for broad coverage: object-oriented, procedural and functional languages (C#, JScript, C++, F#, COBOL, J#, etc.
    [Show full text]
  • 1. Introduction to the Common Language Infrastructure
    Miller-CHP1.fm Page 1 Wednesday, September 24, 2003 1:50 PM 1. Introduction to the Common Language Infrastructure The Common Language Infrastructure (CLI) is an International Standard that is the basis for creating execution and development environments in which languages and libraries work together seamlessly. The CLI specifies a virtual execution system that insulates CLI- compliant programs from the underlying operating system. Where virtual execution sys- tems are developed for different operating systems, programs written with CLI-compliant languages can be run in these different systems without recompiling, or worse, rewriting. Programming with CLI-compliant languages ultimately gives the programmer a simple but rich development model, allowing development in multiple languages, promoting code reuse across languages, and removing most of the plumbing required in traditional programming. The CLI makes it possible for modules to be self-registering, to run in remote processes, to handle versioning, to deal with errors through exception handling, and more. This book, by amplifying the standard, provides a blueprint for creating the infrastructure for this simpler programming model across languages and across platforms. Because the theme of the CLI is broad reach, it also includes provisions for running modules compiled by existing languages into “native code”—machine code targeted at a specific system. This is called unmanaged code, as opposed to the managed code that is CLI-compliant. This book also describes what is required of languages to be CLI-compliant, and what library developers need to do to ensure that their libraries are accessible to any program- mer writing in any CLI-compliant language.
    [Show full text]
  • Shared Source CLI 2.0 Internals
    Shared Source CLI 2.0 Internals Joel Pobar, Ted Neward with David Stutz and Geoff Shilling Table of Contents PREFACE ..................................................................................................................................................... 1 Who Should Read This Book ..................................................................................................................... 4 How This Book Is Structured ..................................................................................................................... 4 Online CLI Resources ................................................................................................................................ 6 Acknowledgments ...................................................................................................................................... 6 1 INTRODUCING THE CLI COMPONENT MODEL ......................................................................... 9 The CLI Virtual Execution Environment ..................................................................................................10 A CLI Implementation in Shared Source: Rotor .......................................................................................17 2 GETTING STARTED WITH ROTOR ................................................................................................25 A Simple Component Assembly ...............................................................................................................25 Observing Managed Execution .................................................................................................................36
    [Show full text]