BS PD ISO/IEC TR 10182:2016基于在以下两个主要领域的标准化方面取得的经验: 信息处理。其中一个领域涉及编程语言。另一个区域由 应用程序实现其目标所必需的服务。这些服务分为多个部分 通过功能接口访问的组，每个组称为系统设施。 系统设施的规范（称为功能规范）定义了一个集合 系统功能，每个功能都执行一些定义良好的服务。由于原则上没有理由不让程序使用特定的系统设施， 无论使用哪种语言编写，系统设施说明符都需要定义 独立于语言的“抽象”功能接口。通过这种方式，特定领域的概念 该领域的专家可以在不考虑语言特性的情况下改进系统设施。一 定义了特定系统设施的内部一致性视图，将系统功能与每个设施联系起来 以一致的方式将系统功能与系统设施内的其他层关联， 包括与整个系统中的其他对象通信的协议。然而，如果这两个领域是独立标准化的，就不可能保证这一点 程序可以从一个操作环境移动到另一个操作环境，即使程序是编写的 使用标准编程语言，仅使用标准系统设施。一种语言的绑定 system facility to a programming language（系统设施到编程语言）提供映射系统设施 功能接口。这允许用这种语言编写的程序访问系统功能 以标准方式构成系统设施。 语言绑定的目的是实现 在特定语言中使用特定功能的程序的可移植性。系统示例 已经为它们开发了语言绑定的工具是GKS、NDL和SQL（参见参考书目）。 预计将需要进一步的语言绑定开发。一些系统设施 目前正在标准化的系统没有语言绑定，并且将提供额外的系统设施 标准化。存在n×m语言绑定的可能性，其中n是语言和 m系统设施的数量。本技术报告的范围是对语言绑定方法进行分类，报告特定的 并为未来的语言绑定标准提供建议指南。请注意，语言绑定和抽象设施接口应具有兼容的运行时 表示，但抽象功能不一定必须用宿主语言编写。 例如，如果应用程序正在使用Pascal语言绑定和相应的 设施是用FORTRAN编写的，在该操作系统中应具有兼容的运行时表示 环境如何实现这种兼容性超出了这些指南的范围。这是 通常是由实现者定义的操作环境的属性，并简要回顾 在本技术报告中。交叉引用:ISO/IEC 1539-1:2010ISO/IEC 1989:2014ISO 6373:1984ISO 7185:1990ISO/IEC 7942-1ISO 8651-1:1988ISO 8651-2:1988ISO 8651-3:1988ISO/IEC 8651-4:1995ISO/IEC 8652:2012ISO 8805:1988ISO 8907:1987ISO/IEC 9075-2ISO/IEC 9075-3ISO/IEC 9075-4ISO/IEC 9075-11ISO/IEC 9593-1ISO/IEC 9593-1ISO/IEC 9593-99-ISO/IEC 10206当前修订版可随时查阅购买本文件时包括购买费用。

BS PD ISO/IEC TR 10182:2016 is based on experience gained in the standardization of two major areas in information processing. One area covers programming languages. The other area is composed of the services necessary to an application program to achieve its goal. The services are divided into coherent groups, each referred to as a SYSTEM FACILITY, that are accessed through a FUNCTIONAL INTERFACE. The specification of a system facility, referred to as a FUNCTIONAL SPECIFICATION, defines a collection of SYSTEM FUNCTIONS, each of which carries out some well-defined service.Since in principle there is no reason why a particular system facility should not be used by a program, regardless of the language in which it is written, it is the practice of system facility specifiers to define an 'abstract' functional interface that is language independent. In this way, the concepts in a particular system facility may be refined by experts in that area without regard for language peculiarities. An internally coherent view of a particular system facility is defined, relating the system functions to each other in a consistent way and relating the system functions to other layers within the system facility, including protocols for communication with other objects in the total system.However, if these two areas are standardized independently, it is not possible to guarantee that programs from one operating environment can be moved to another, even if the programs are written in a standard programming language and use only standard system facilities. A language binding of a system facility to a programming language provides language syntax that maps the system facility's functional interface. This allows a program written in the language to access the system functions constituting the system facility in a standard way. The purpose of a language binding is to achieve portability of a program that uses particular facilities in a particular language. Examples of system facilities that have had language bindings developed for them are GKS, NDL, and SQL (see Bibliography). It is anticipated that further language binding development will be required. Some system facilities currently being standardized have no language bindings and additional system facilities will be standardized. There is a possibility of n × m language bindings, where n is the number of languages and m the number of system facilities.The scope of this Technical Report is to classify language binding methods, reporting on particular instances in detail, and to produce suggested guidelines for future language binding standards.Note that the language bindings and the abstract facility interfaces shall have a compatible run time representation, but the abstract facility does not necessarily have to be written in the host language. For example, if the application program is using a Pascal language binding and the corresponding facility is written in FORTRAN, there shall be a compatible run time representation in that operating environment. How this compatibility is achieved is outside the scope of these guidelines. This is generally a property of the operating environment defined by the implementor, and is reviewed briefly in this Technical Report.Cross References:ISO/IEC 1539-1:2010ISO/IEC 1989:2014ISO 6373:1984ISO 7185:1990ISO/IEC 7942-1ISO 8651-1:1988ISO 8651-2:1988ISO 8651-3:1988ISO/IEC 8651-4:1995ISO/IEC 8652:2012ISO 8805:1988ISO 8907:1987ISO/IEC 9075-1ISO/IEC 9075-2ISO/IEC 9075-3ISO/IEC 9075-4ISO/IEC 9075-11ISO/IEC 9593-1ISO/IEC 9593-3ISO/IEC 9593-4ISO/IEC 9899:2011ISO/IEC 10206:1991All current amendments available at time of purchase are included with the purchase of this document.