Information technology - Programming languages, their environments and system software interfaces - Guidelines for language bindings
Introduction: This Technical Report is a compilation of the experience and knowledge gained by the members of ISO/IEC JTC1/SC22/WG11 (Techniques for Bindings) from the generation of programmers’ interfaces to FUNCTIONAL INTERFACE STANDARDS. Although current experience was derived from the fields of computer graphics and database management, the problems discussed are thought to be generally applicable for mappings of other functional interface standards to programming languages. This Technical Report is intended a) to identify the problems and conflicts which shall be resolved; b) to suggest guidelines for future use; c) to provide scope and direction to required additional work, such as common procedural calling mechanisms and data types; and d) as a historical record of past experiences and decisions. This Technical Report is incomplete; the authors have concentrated on those areas where experience and expertise was readily available. The ideas and issues brought forward here emerged from more than 10 years of work, and are represented in International Standards. Clause 3 of this Technical Report contains the results of a survey of current methods used for language binding development. Characteristics of each method are given, followed by reasons for the selection of the method. Application of the methods has suggested some guidelines that are presented in Clause 4. Clauses 3 and 4 contain documentation of the current state of language binding efforts; Clause 5 addresses future direction
Scope: This Technical Report 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