C++/CLI语言规范：ECMA-372标准详解

需积分: 10 45 浏览量更新于2024-07-18 收藏 1.51MB PDF 举报

ECMA-372标准，全称为"C++/CLI语言规范第一版（2005年12月）"，是为C++/CLI绑定的实现制定的要求文档。C++/CLI是一种将C++与.NET框架结合的语言，它允许开发者在.NET平台上编写混合模式代码，即同时使用C++和.NET组件。该标准的主要目标是确保不同实现之间的一致性和互操作性。 1. **范围和目的**：标准定义了C++/CLI语言的设计和行为，包括其语法、类型系统和关键特性，以便于开发人员理解和遵循。它涵盖了从基础类型和转换规则到高级概念如参数传递、内存管理、表达式和语句结构的全面指南。 2. **规范和兼容性**：实施者必须满足标准中列出的强制性要求，比如实现完整的C++/CLI语言支持。同时，标准也允许对某些规定进行适当的调整，但必须确保这些调整不会破坏语言的整体一致性。 3. **术语和符号约定**：规范提供了明确的定义和符号约定，帮助读者理解复杂的概念和语法结构，如指针、引用和null值的处理。 4. **语言概述**：规范首先介绍如何开始使用C++/CLI，强调了不同类型，包括基本类型、CLI数组、类型系统的统一以及对.NET和C++特性的集成。此外，还详细讨论了参数传递、自动内存管理和异常处理。 5. **语言核心元素**： - **类型系统**：C++/CLI支持多种类型，包括fundamental types（基本类型）、CLI数组、指针和引用，以及针对.NET环境的特定类型。 - **函数和方法**：规范定义了各种函数和方法的声明、参数传递方式（native和ref）、类成员（字段、构造函数、析构函数等）以及事件和委托的使用。 - **价值类（value classes）**：C++/CLI允许创建轻量级的对象，它们在栈上分配，适合于性能敏感的应用场景。 6. **接口和混合编程**： C++/CLI支持接口的定义和使用，这对于编写可重用且面向.NET框架的库或组件至关重要。通过混合使用C++和.NET代码，开发人员能够充分利用两者的优点。 ECMA-372标准是C++/CLI语言的基础，对于开发者而言，理解和遵循这个规范至关重要，因为它定义了C++/CLI在.NET平台上的行为准则，有助于确保代码的正确性、兼容性和性能。通过学习和遵循这些规则，开发者可以有效地在C++和.NET世界之间构建无缝交互的应用程序。

C++/CLI Language Specification

2. Conformance

Clause §1.4, “Implementation compliance”, of the C++ Standard applies to this Standard.

C++/CLI Language Specification

4. Definitions

For the purposes of this Standard, the following definitions apply. Other terms are defined where they appear

in italic type or on the left side of a syntax rule. Terms explicitly defined in this Standard are not to be

presumed to refer implicitly to similar terms defined elsewhere. Terms not defined in this Standard are to be

interpreted according to the C++ Standard, ISO/IEC 14882:2003.

application — Refers to an assembly that has an entry point. When an application is run, a new application

domain is created. Several different instantiations of an application can exist on the same machine at the

same time, and each has its own application domain.

application domain — An entity that enables application isolation by acting as a container for application

state. An application domain acts as a container and boundary for the types defined in the application and the

class libraries it uses. A type loaded into one application domain is distinct from the same type loaded into

another application domain, and objects on the CLI heap are not directly shared between application

domains. Each application domain has its own copy of static variables for these types, and a static

constructor for a type is run at most once per application domain. Implementations are free to provide

implementation-specific policy or mechanisms for the creation and destruction of application domains.

assembly — Refers to one or more files that are output by the compiler as a result of program compilation.

An assembly is a configured set of loadable code modules and other resources that together implement a unit

of functionality. An assembly can contain types, the executable code used to implement these types, and

references to other assemblies. The physical representation of an assembly is defined by the CLI Standard

(§3). Essentially, an assembly is the output of the compiler. An assembly that has an entry point is called an

application. (See also “metadata”.)

attribute — A characteristic of a type and/or its members that contains descriptive information. While the

most common attributes are predefined, and have a specific encoding in the metadata associated with them,

user-defined attributes can also be added to the metadata.

boxing — An explicit or implicit conversion from any value class type

V to type V^, in which a V box is

allocated on the CLI heap, and the value is copied into that box. (See also “unboxing”.)

CIL — Common Intermediate Language, the instruction set of the Virtual Execution System. This

instruction set is defined in Partition III of the CLI Standard (§3).

CLI array — A CLI-specific array. A Standard C++-style array is referred to as a native array or, more

simply, array, whenever the distinction is needed. A CLI array differs from a native array in that the former

is allocated on the CLI heap, and can have a rank other than one.

CLS compliance — The Common Language Specification (CLS) defines language interoperability rules,

which apply only to items that are visible outside of their defining assembly. CLS compliance is described in

Partition I of the CLI Standard (§3).

definition, out-of-class — A synonym for what Standard C++ calls a “non-inline definition”.

delegate — A ref class such that an instance of it can encapsulate one or more functions. Given a delegate

instance and an appropriate set of arguments, one can invoke all of that delegate instance’s functions with

that set of arguments.

event — A member that enables a class or a CLI object to provide notifications.

field — A synonym for what Standard C++ calls a “data member”.

function, abstract — A synonym for what Standard C++ calls a “pure virtual function”.

Definitions

garbage collection — The process by which memory allocated from the CLI heap is automatically

reclaimed on the CLI heap.

gc-lvalue — An expression that refers to an entity that might be allocated on the CLI heap. (See also

“lvalue”.)

handle — A handle is called an “object reference” in the CLI specification. For any CLI class type

T, the

declaration

T^ h declares a handle h to type T, where the object to which h is capable of pointing resides on

the CLI heap. A handle tracks, is rebindable, and can point to a whole object only. (See also “type,

reference, tracking”.)

heap, CLI — The storage area (accessed by

gcnew) that is under the control of the garbage collector of the

Virtual Execution System as specified in the CLI. (See also “heap, native”.)

heap, native — The storage area (accessed by

new) as defined in the C++ Standard (§18.4). (See also “heap,

CLI”.)

instance — An instance of a type.

lvalue — This has the same meaning as that defined in the C++ Standard (§3.10). (See also “gc-lvalue”.)

metadata — Data that describes and references the types defined by the Common Type System (CTS).

Metadata is stored in a way that is independent of any particular programming language. Thus, metadata

provides a common interchange mechanism for use between tools that manipulate programs (such as

compilers and debuggers) as well as between these tools and the Virtual Execution System.

pinning — The process of (temporarily) keeping constant the location of an object that resides on the CLI

heap, so that object’s address can be taken with that address remaining constant.

property — A member that defines a named value and the functions that access that value. A property

definition defines the accessing contracts on that value. Hence, the property definition specifies the

accessing functions that exist and their respective function contracts.

rebinding —The act of making a handle or pointer refer to the same or another object on the CLI heap.

rvalue — This has the same meaning as that defined in the C++ Standard (§3.10).

tracking — The act of keeping track of the location of an object that resides on the CLI heap; this is

necessary because such objects can move during their lifetime (unlike objects on the native heap, which

never move). Tracking is maintained by the Virtual Execution System during garbage collection. Tracking is

an inherent property of handles and tracking references.

type, boxed — See “type, value class, boxed”.

type, class, any — Any CLI or native class type.

type, class, CLI class — A ref class type, a value class type, or an interface class type.

type, class, interface — A type that declares a set of virtual members that an implementing class shall

define. An interface class type is a CLI type.

type, class, native — An ordinary Standard C++ class (declared using

class, struct, or union).

type, class, ref — A type that can contain fields, function members, and nested types. A ref class type is a

CLI type.

type, class, value — A type that can contain fields, function members, and nested types. Instances of a value

class type are values. Since they directly contain their data, no heap allocation is necessary. A value class

type is a CLI type.

type, class, value, boxed — A boxed value class is an instance of a value class on the CLI heap. For a value

class

V, a boxed value class is always of the form V^.

type, class, value, simple — The subset of value class types that can be embedded in a native class type and

allocated with the

new operator.

剩余303页未读，继续阅读

z_g_j

粉丝: 0
资源: 5

C++/CLI语言规范：ECMA-372标准详解

Ecma-372_C++_CLI

ECMA-335 ECMA-335

ecma-262.pdf下载

ECMA-262第六版

javascript.API 官方文档

Content-Type:application/json是否是标准的http规范

stm32伺服电机控制器

如何查看每年发布的EcmaScript有哪些新内容

最新资源