ISO/IEC 9593-3:1990
(Main)Information technology — Computer graphics — Programmer's Hierarchical Interactive Graphics System (PHIGS) language bindings — Part 3: ADA
Information technology — Computer graphics — Programmer's Hierarchical Interactive Graphics System (PHIGS) language bindings — Part 3: ADA
Technologies de l'information — Infographie — Interfaces langage avec PHIGS — Partie 3: ADA
General Information
Relations
Standards Content (Sample)
lso/lEc
INTERNATIONAL
9593-3
STANDARD
First edition
1990-04- 15
Information technology - Computer graphics -
Programmer’s Hierarchical Interactive Graphits
System (PHIGS) language bindings Y
Part 3 :
Ada
Technologies de Knformation - lnfographie - lnterfaces langage avec PHIGS -
Partie 3 : Ada
Reference number
ISO/IEC 9593-3 : 1990 (EI
ISOAEC 959393 : 1990 (E)
Contents
iv
Foreword
V
Introduction
1 Scope
2 Normative references
3 Principles
3.1 Conformance .
3.2 Implications of the Language .
..........................................................................................................
3.2.1 Functional Mapping
......................................................................
3.2.2 Implementation and Host Dependencies
..................................................................................................................
3.2.3 Error Handling
....................................................................................................................
3.2.4 Data mapping
......................................................................................................................
3.2.5 Multi-tasking
3.2.6 Packaging .
................................................................................
3.2.7 Application Program Environment
3.2.8 Registration .
4 Tables
. . . . . . . . . . . . . . . .*.
4.1 Abbreviations used in nrocedure names
A
4.1.1 List of procedures using the abbreviations .
.........................................................................................
4.1.2 Alphabetical by bound name
Alphabetical PHIGS functions . 15
4.1.3
4.2 Data type definitions .
.......................................................... 16
4.2.1 Abbreviations used in the data type defmitions
.............................................................................. 16
4.2.2 Alphabetical list of type deftitions
............................................................. 66
4.2.3 Alphabetical List of Private Type Deftitions
........................................................................................ 68
4.2.4 List of Constant Declarations
........................................................................................ 69
4.2.5 PHIGS Configuration Values
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.3 Error Codes
. . . . . . . . . . . . . . . . . . . . . . . . .~. 72
4.3.1 Precluded Error Codes
0 ISO/IEC 1990
All rights reserved. No part of this publication may be reproduced or utilized in any form or by
any means, electronie or mechanical, including photocopying and microfilm, without Permission
in writing from the publisher.
ISO/IEC Copyright Office l Case postale 56 l CH-121 1 Geneve 20 l Switzerland
. Printed in Switzerland
ii
ISO/IEC 9593-3 : 1990 (E)
5 Functions in the Ada Binding of PHIGS
.......................................................................................................................
5.1 Control functions
.......................................................................................................
5.2 Output primitive functions
.............................................................................................
5.3 Attribute specification functions
..................................................................................
5.4 Transformation and clipping functions
......................................................................................................
5.5 Structure content functions
............................................................................................
5.6 Structure manipulation functions
.......................................................................................................
5.7 Structure display functions
......................................................................................................
5.8 Structure archive functions
5.9 Input functions .
5.10 Metafile functions .
5.11 Inquiry functions .
.........................................................................................................
5.12 Error control functions
...................................................................................................
5.13 Special interface functions
............................................................................................................
5.14 Additional Functions
.............................................
5.14.1 Subprograms for Manipulating Input Data Records
.........................................................
5.14.2 PHIGS Generic Coordinate System Package
........................................................................
5.14.3 PHIGS Generic List Utility Package
...........................................................................
5.14.4 PHIGS Name Set Facility Package
..............................................................
5.14.5 Deallocation of structure element records
5.14.6 Metafile Function Utilities .
5.15 Conformal Variants . . . . . . . . . . . .Y.
Annexes
A Compilable PHIGS Specification
_ B Cross Reference Listing of Implementation Defined Items
C Example Programs
................................................................................................
C.l Example Program 1: STAR
................................................................................................
C.2 Example Program 2: IRON
...................................................................................
C.3 Example Program 3: DYNASTAR
POLYLINE .
C.4 Example Program 4: TRANSFORM
.....................................................................
C.5 Example Program 5: SHOW LINETWES
D PHIGS Multi-Tasking
E Index
. . .
ISO/IEC 9593-3 : 1990 (E)
Foreword
ISO (the International Organization for Standardization) and IEC (the International Electrotechnical Commission)
together form a System for worldwide standardization as a whole. National bodies that are members of ISO or IEC
participate in the development of International Standards through technical committees established by the respective
organization to deal with particular fields of technical activity. ISO and IEC technical committees collaborate in fields of
mutual interest. Other international organizations, governmental and non-governmental, in liaison with ISO and IEC, also
take part in the work.
In the field of information technology, ISO and IEC have established a joint technical committee, ISO/IEC JTC 1. Draft
International Standards adopted by the joint technical committee are circulated to national bodies for approval before
their acceptance as International Standards. They are approved in accordance with procedures requiring at least 75 ?70
approval by the national bodies voting.
International Standard ISOAEC 9593-3 was prepared by Technical Committee ISOAEC JTC 1, Information technology.
ISOAEC 9593-3 : 1990 (E)
Introduction
ISO/IEC 9592 is specified in a language independent manner and needs to be embedded in language
dependent layers (language bindings) for use with particular programming languages.
The purpose of this part of ISO/IEC 9593 is to define a Standard binding of PHIGS to the Ada Computer
programming language.
This page intentionally left blank
ISO/IEC 9593-3 : 1990 (E)
INTERNATIONAL STANDARD
Information technology - Computer graphics -
~
Programmer’s Hierarchical Interactive Graphits System
(PHIGS) language bindings -
Part 3 :
Ada
1 Scope
ISO/IEC 9592 specifies a language independent nucleus of a graphics System. For integration. into a
programming language, PHIGS is embedded in a language dependent layer obeying the particular conventions
of that language. This part of ISO/IEC 9593 specifies such a language dependent layer for the Ada Computer
programming language.
ISO/IEC 9593-3 : 1990 (E)
Normative references
2 Normative references
The following Standards contain provisions which, through reference in this text, constitute provisions of this
part of ISO/IEC 9593. At the time of publication, the editions indicated were valid. All Standards are subject
to revision, and Parties to agreements based onthis part of ISO/IEC 9593 are encouraged to investigate the
possibility of applying the most recent editions of the Standards listed below. Members of IEC and ISO
maintain registers of currently valid International Standards.
ISO 8652 : 1987, Programming languages -Ada (Endorsement of ANSI Standard 1815A-1983).
Computer gaphics - Programmerk Hierarchical
ISO/IEC 95924 : 1989, Information processing systems -
Interactive Graphits System (PHIGS) - Part 1: Functional description.
ISO/IEC 9593-3 : 1990 (E)
Principles
3 Principles
The PHIGS Binding to Ada is intended to be implementation independent except as it tan be adapted by the
PHIGS CONFIGURATION package. The PHIGS Binding to Ada makes no assumptions concerning the
availabixty of implementation dependent facilities defined by the Ada language. It does, however, limit the use
of multi-tasking as described in 3.2.5. The Ada Compiler shall be able to support the number of declarations
contained in this PHIGS Binding to Ada.
This binding does not make any assumptions regarding the machine representation of the predefined Ada
numeric types.
This binding assumes that the application programmer will supply an error file name, archive file names, and
connection identifiers that are in an acceptable format for the Ada implementation.
This binding makes no assumptions ,regarding the format of a string specifying an error file name, archive file
names, or connection identifiers for devices or metafiles.
3.1 Conformance
This binding incorporates the rules of conformance defined in the PHIGS Standard (ISO/IEC 9592) for
PHIGS implernentations, with these additional requirements specifically defined for Ada implernentations of
PHIGS.
The following criteria are established for determining conformance or non-conformance of an implementation
to this binding:
- The semantics of an implementation shall be those stated in ISO/IEC 9592 as modified or extended for
Ada as stated in this part of ISO/IEC 9593.
- The package corresponding to PHIGS shall be an available Ada library unit, with all names as specifred
by this part of ISO/IEC 9593.
3.2 Implications of the Language
3.2.1 Functional Mapping
The functions of PHIGS are all mapped to Ada procedures. The mapping utilizes a one-to-one correspondence
between the PHIGS functions and Ada procedures except for the PHIGS function INQUIRE TEXT EXTENT.
This function is mapped to two overloaded Ada functions each named INQ TEXT EXTENT one which
ISOAEC 9593-3 : 1990 (E)
Implications of the Language Principles
supports modelling text and one which supports annotation text. Certain functi .ons required by the binding but
not defined by PHIGS are mapped to Ada functions and procedures.
3.2.2 Implementation and Host Dependencies
.
There are a number of implementation and host dependencies associated with the Ada Compiler and runtime
System used. These will affect the portability of application programs and their use of PHIGS. The application
programmer should follow accepted practices for ensuring portability of Ada programs to avoid introducing
Problems when rehosting the application on another System. Implementation dependencies include runtime
storage management and processor management. ,
3.23 Error Handling
The inquiry functions utilize error indicator Parameters for the error returns, and do not raise Ada exceptions.
The application program shall ensure that these error indicators are checked before attempting to access other
Parameters, since Ada implernentations are not required to raise an exception if an undefined value is accessed.
The error handling requirements of PHIGS tan be summ arized as follows:
By default, a procedure named ERROR HANDLING will be provided that simply reports the error by
1.
calling ERROR LOGGING. This is calkd from the PHIGS function that detects the error.
2. The ERROR HANDLING procedure may be replaced by one defined by the User.
The procedure ERROR HANDLING is defined as a library subprogram:
with PHIGS TYPES;
use PHIGS TYPES;
procedure ERROR HANDLING
(ERROR INDICÄTOR : in ERROR NUMBER;
PHIGS ~WNCTION : in STRING;
: inFILE ID := DEFAULT ERROR FILE);
ERROR FILE
--
The procedure ERROR HANDLING is defined as a library subprogram,
--
and is not declared withii package PHIGS.
This binding defines two different bodies for this subprogram; each s
...
Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.