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

Status
Published
Publication Date
11-Apr-1990
Current Stage
9093 - International Standard confirmed
Start Date
06-Jan-2005
Completion Date
08-Dec-2021
Ref Project

RELATIONS

Buy Standard

Standard
ISO/IEC 9593-3:1990 - Information technology -- Computer graphics -- Programmer's Hierarchical Interactive Graphics System (PHIGS) language bindings
English language
285 pages
sale 15% off
Preview
sale 15% off
Preview

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
---------------------- Page: 1 ----------------------
ISOAEC 959393 : 1990 (E)
Contents
Foreword
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

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
---------------------- Page: 2 ----------------------
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 ...........................................................................................................................

106

5.10 Metafile functions .................................................................................................................

107

5.11 Inquiry functions ....................................................................................................................

132

.........................................................................................................

5.12 Error control functions
133

...................................................................................................

5.13 Special interface functions
134

............................................................................................................

5.14 Additional Functions
134
.............................................
5.14.1 Subprograms for Manipulating Input Data Records
138
.........................................................
5.14.2 PHIGS Generic Coordinate System Package
141
........................................................................
5.14.3 PHIGS Generic List Utility Package
144
...........................................................................
5.14.4 PHIGS Name Set Facility Package
147
..............................................................
5.14.5 Deallocation of structure element records
149

5.14.6 Metafile Function Utilities .........................................................................................

149

5.15 Conformal Variants . . . . . . . . . . . ..Y................................................................................................

Annexes
151
A Compilable PHIGS Specification
243
_ B Cross Reference Listing of Implementation Defined Items
245
C Example Programs
245

................................................................................................

C.l Example Program 1: STAR
248

................................................................................................

C.2 Example Program 2: IRON
255

...................................................................................

C.3 Example Program 3: DYNASTAR
261
POLYLINE .........................................................
C.4 Example Program 4: TRANSFORM
269
.....................................................................
C.5 Example Program 5: SHOW LINETWES
274
D PHIGS Multi-Tasking
279
E Index
. . .
111
---------------------- Page: 3 ----------------------
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.

---------------------- Page: 4 ----------------------
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.
---------------------- Page: 5 ----------------------
This page intentionally left blank
---------------------- Page: 6 ----------------------
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.
---------------------- Page: 7 ----------------------
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.
---------------------- Page: 8 ----------------------
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

---------------------- Page: 9 ----------------------
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

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 shall be supplied by the implementation.

The default body is the one required by PHIGS semantics. It simply calls ERROR LOGGING and returns.

The second body calls ERROR LOGGING and then raises the exception PHIGS ERROR. The PHIGS

function shall be written so as nÖt to handle PHIGS ERROR (this is a requirementof the implementation).

Thus, by Ada rules, the exception will be propagatedback to the application program that called the PHIGS

function in which the error was detected.

The means by which the user replaces the default body by either the exception-raising version or another one of

his or her choosing is dependent upon the Ada library manager. Some implernentations support multiple

Versions of a body with a Single specification or otherwise allow hierarchical libraries with the sharing of

common units. In other implernentations, it may be necessary to duplicate the PHIGS library for each version

of ERROR HANDLING.
3.2.4 Data mapping

The simple and compound data types of PHIGS are bound to a variety of Ada scalar and compound types.

Constraints on permitted values are reflected where possible in the type definitions. The general

correspondence between the PHIGS data types and Ada binding data types is summarized below:

---------------------- Page: 10 ----------------------
ISO/IEC 9593-3 : 1990 (E)
Implications of the Language
Principles
- PHIGS integer types (1) are mapped to Ada integer types.
- PHIGS real types (R) are mapped to Ada floating-Point types.

- PHIGS string types (S) are mapped to the predefined Ada type STRING, or to a type providing for

variable length strings.
PHIGS Point types (P2, P3) are mapped to Ada record types.
PHIGS vector types (V2, V3) are mapped to Ada record types.
- PHIGS enumeration types (E) are mapped to Ada enumeration types.
The PHIGS name set composite type
- PHIGS name types (NM) are mapped to an Ada integer type.
A set of subprograms for operating on objects of this
SET(NM) is mapped to an Ada private type.
private type is explicitly defined by this binding.
- PHIGS filter types (FR) are mapped to an Ada record type.
PHIGS pick paths are mapped to an
- PHIGS pick path item type (PP) is mapped to an Ada record type.
Ada array type.
- PHIGS element reference type (ER) is mapped to an Ada record type.
- PHIGS half-space types (HS2, HS3) are mapped to Ada record types.
- PHIGS font/precision pair type (FP) is mapped to an Ada record type.
- PHIGS structure element type (SE) is mapped to an Ada record type.
- PHIGS posted structure type (PS) is mapped to an Ada record type.
- PHIGS bounding range types (B) are mapped to Ada record types.
- PHIGS colour specification type (CLR) is mapped to an Ada record type.
- PHIGS chromaticity coefficient type (CC) is mapped to an Ada record type.
- PHIGS connection identifier type (C) is mapped to the Ada STRING type.
- PHIGS file types (F) are mapped to Ada STRING types.
- PHIGS workstation type (W) is mapped to an Ada integer type.

- PHIGS modehing clipping volume type (MCV) is not used by the binding. Implernentations tan map

this type to an implementation specific private type.

- PHIGS generalized drawing primitive identifier types (G2, G3) are mapped to Ada integer types.

- PHIGS generalized structure element identifier type (GS) is mapped to an Ada integer type.

- PHIGS archive file identifier type (AI) is mapped to an Ada integer type.
- PHIGS pick identifier type (PI) is mapped to an Ada integer type.
PHIGS escape identifier type (EI) is mapped to an Ada integer type.

- PHIGS function name type (FN) is mapped to an Ada type providing for variable length strings.

---------------------- Page: 11 ----------------------
ISO/IEC 9593-3 : 1990 (E)
Implications of the Language Principles
- PHIG workstation identifier type (WI) is mapped to an Ada integer type.
- PHIGS tuples are mapped to Ada record types.
- PHIGS matrices are mapped to Ada array types.
ng for

- PHIGS arrays are mapped to either an unconstrained Ada array type, or to a record providi

variable length arrays.

- PHIGS lists are mapped to an Ada private type declared in the generic PHIGS LIST UTILITIES

package.

- PHIGS set are mapped to Ada private types with generic accessing functions provided

necessary.

- PHIGS data records are mapped to Ada private types. In some cases, a set of subprograms for

operating on the data records is explicitly defined by this binding. This is because the content and

An implementation of PHIGS may provide
structure of the data record is implementation dependent.
other subprograms for manipulating implementation dependent data records.

Additional types used by the binding are declared as needed in a manner compatible with the PHIGS types.

3.2.5 Multi-tasking

The Ada language definition provides explicit support for concurrency. The Ada tasking model includes

facilities for declaring and allocating tasks, and operations allowing intertask communication and

synchronization.

The PHIGS Standard, and hence this binding Standard, neither requires nor prohibits an implementation from

protecting against Problems which could arise from asynchronous access to the PHIGS data structures from

concurrent tasks. Implernentors of PHIGS should provide information in the user’s documentation regarding

whether protection against such Problems is implemented.

Annex D contains guidelines for implementors who want to support multi-tasking application programs. This

annex does not form an integral part of the binding Standard, but provides additional information.

32.6 Packaging

The PHIGS Standard defines all of its graphic functionality as a cohesive whole. An implementation of PHIGS

shall implement the entire functionality of PHIGS. To support this concept, this binding defines a Single Ada

package which corresponds to all of the PHIGS functionality. This package is named

package PHIGS is . . . end PHIGS;

Associated with this package is a data type package which provides the type declarations as defined in 4.2 and

the exception defined in 4.3. This package is
package PHIGS TYPES is . . . end PHIGS TYPES;
A minimal program referencing PHIGS is shown below.
with PHIGS,
PHIGS TYPES;
procedure APPLICATION is
begin
---------------------- Page: 12 ----------------------
ISO/IEC 9593-3 : 1990 (E)
Implications of the Language
Principles
null;
end APPLICATION;
Several additional Ada packages are defined in this binding. These packages are
- generic package PHIGS COORDINATE SYSTEM
- generic package PHIGS LIST UTILITIES
- package PHIGS NAME SET FACILITY
- package PHIGS CONFIGURATION
in the PHIGS TYPES package described above.
These packages support the declaration types

PHIGS COORDINATE SYSTEM is a generic package which defines & assortment of types supporting each

of the FHIGS coordinatc Systems. PHIGS LIST UTILITIES is also a generic package which provides type

declarations and operations for list tkes Kuhich correspond to the PHIGS list types. The

PHIGS NAME SET FACILITY package defmes private types for name sets and provides functions for

buildinc and manipulating name Sets. The PHIGS CONFIGURATION package sets implementation

dependent limit values for various types defmed in this biñding. The PHIGS CONFIGURATION package also

provides for possible application modification of these limits.
3.2.7 Application Program Environment

An application program utilizing an Ada implementation of PHIGS will need to be aware of the environment in

which both PHIGS and the application program reside.

One aspect of the environment is the Ada program library. The Ada language requires that the application

program have access to the program library in which the PHIGS Software resides. The Ada Standard ISO 8652

does not specify whether there is a Single library or multiple libraries, or how access to the libraries is granted

or managed. The user’s documentation for the PHIGS implementation should specify where the PHIGS library

exists in the System, and how access to the library is acquired.

Input/Output interfaces are also implementation-dependent, and are required to be described in the user’s

documentation. Besides the obvious graphics device interface information, interfaces to the file System shall be

included in the documentation. Specifically, this includes the interface to the PHIGS error file, archive files,

and metafile storage.

Subclause 3.2.2 discusses implications about the application program environment which may also apply to

application programs.
3.2.8 Registration’

PHIGS reserves certain value ranges for registration as graphical items. The registered graphical items will be

bound to Ada (and other programming languages). The registered item bindings will be consistent with the

binding presented in this document.

1) I?or the purpose of this International Standard and according to the rules for the designation and Operation of registration authorities

in the ISO/IEC JTC 1 procedures, the ISO and IEC Councils have designated the National Institute of Standards and Technologe

(National Computer Systems Laboratory) A-266 Technology Building, Gaithersburg, MD 20899, USA, to act as registration authority.

---------------------- Page: 13 ----------------------
ISO/IEC 9593-3 : 1990 (E)
Implications of the Language
Tables
4 Tables
4.1 Abbreviations used in procedure names
ASF aspect Source flag
CHAR Character
ESC escape
GDP generalized drawing primitive
GSE generalized structure element
HLHSR hidden line/hidden surface removal
INQ inquire
PHIGS Programmer’s Hierarchical Interactive Graphits System
U unregistered
WS workstation
4.1.1 List of procedures using the abbreviations
ASF SETJNDMDUAL ASF
CHAR SET ANNOTATION TEXT CHAR HEIGHT
SET-ANNOTATION-TEXT-CHAR-UP VECI’OR
SET.-CHAR EXPANSIONjÄ~Oi? -
SET-CHAR-HEIGHI-’
SET-WAR-SPACING
SET;CHARIUP VE(TTOR
ESC PHIGSJSCAPE.GENERALIZED ESC
PHIGSJSC < name of the escape Frocedure > ESC
PHIGSJJES?- c name of the escape procedure > .ESC
INQ GDP (2D)
GDP
INQ-GDP (3D)
INQ-LIST OF AVAILABLE GDP (2D)
INQ-LIST-OF-AVAILABLE-GDP (3D)
PHIGS GDP.GENERALIZED GDP
PHIGSIGDP-< name of the GGP procedure > .GDP
PHIGSUGDP-< name of the GDP procedure > .GDP
GSE INQ GSE FACILITIES
INQ-LIS’l?OF AVAILAiLE GSE
PHI& G~E.G?kNERALIZE~ GSE
PHIGSIGSE-< name of the GS%5 procedure > .GSE
PHIGSJJGSE- < name of the GSE procedure > .GSE
HLHSR INQ-HLHSR-FACILITIES
INQ HLHSR MODE
SET-HLHSR-IDENTIFIER
SET-HLHSR-MODE
INQ-ALLCONFLICI’ING STRUCTURES
INQ
---------------------- Page: 14 ----------------------
c(cIm
b4cIWHH
uc(nw zzz ZZZZ
zzzzz
zzzz Qcm QQQQ
QQQQQ
I I I
lQIQIQIQl nncl dn’rb
dz’ch’o
WS?
*w rgzz
sj;,m
@EX
,dC
w#gg
l~ly m”IM
pp- IV7
8 UUI I
2!z
Bmq
’ ‘~‘*‘* . !F
cf 8 F
dL;P
fb-
-tl
ff!
-agq
-“w ga,&l
M’r
bi 3
m 0
Eis
O>Q
k i$ zdr
Cl d
” ti
zEl
---------------------- Page: 15 ----------------------
ISOAEC 9593-3 : 1990 (E)
Abbreviations used in procedure
cames Tables
INQPHIGS-FACILITIES
INQ PICK DEVICE STATE (2D)
INQ-PICK-DEVICE-STATE (3D)
INQ-POLTLINE F&ILITIES
INQPOLYLINI-REPRESENI’ATION
INQ-POLYMAmR FACILITIES
INQ-POLYMARKER-REPRESENTA’IION
INQPOSTED STRU-CTURES
INQ-PREDEHNED COLOUR REPRESENTATION
INQ-PREDEFINED-EDGE REPRESENTATION
INQ-PREDEFINED-INTEIÜOR REPRESENTATION
INQ-PREDEFINED-PA’ITERN -iXEPRESENTATION
INQ-PREDEFINED-POLYLIm REPRESENTATION
INQ-PREDEFINED-POLYMA-R REPRESENTATION
INQ-PREDEFINED-TEXT REPRESi%I’ATION
INQ-PREDEFINED-VIEW-REPRESENTATION
INQ-SET OF OPEfl WS -
INQ-SET-OF-WS Tö WHICH POSTED
INQ-STRiNG-DE%ICi? STAm(2D)
INQ-STRING-DEVICE-STATE (3D)
INQ-STROE DEVICE STATE (2D)
INQ-STROKE-DEVICE-STATE (3D)
INQSTRUmRE IDE-mFIERS
INQ-STRUCI’URE-STATE VALUE
INQ-STRUCTURE-STATU.3
INQSYSTEM STA?& VALUE
INQITEXT-E%TENT (text)
INQ TEXT EXTENT (annotation text)
INQ-TEXT-FACILITIES
INQ-TEXT-REPRESENTATION
INQ-VALUÄTOR DEVICE STATE (2D)
INQ-VALUATOR-DEVICE-STATE (3D)
INQ-VIEW FACIciTIES -
INQ-VIEW-REPRESENTATION
INQ-WS CÄTEGORY
INQ-WS-CLASSIFICATION
INQ-WS-CONNECIION AND TYPE
INQ-WS-STATE TABLE LENGTHS
INQ-WS-STATE-VALUE
INQ-WS-TRANSFORMATION (2D)
INQ-WS-TRANSFORMATION (3D)
PHIGS CLOSE PHIGS
EMERGENCY CLOSE PHIGS
INQ PHIGS FÄCILITIB
OP& PHIGS
U PHIGS UESC c name of the escape procedure > ESC
PHIGSUGDP < name of the GDP orocedure > .GDP
PHIGS-UGSE -< name of the GSE irocedure > .GSE
WS CLOSE WS
INQ DkNAMICS OF WS ATTRIBUTES
INQ-LIST OF AvAItiBcE WS TYPES
INQSETÖFÖPEN WS - -
INQSET-OFWS Tö WHICH POSTED
INQ-WS cA’-J%GöRY- -
INQ-WS-CLASSIFICATION
INQ-WS-CONNEmON AND TYPE
INQ-WS-STATE TABLI? LENGTHS
INQ-WS-STA=-VALUE
INQ-WS-TRANSFORMATION (2D)
INQ-WS-TRANSFORMATION (3D)
OPE!& WS
SET WS VIEWPORT(2D)
SET.-WS-VIEWPORT (3D)
SET-WS-WINDOW (2D)
SET-WS-WINDOW (3D)
UPIj-Am-WS
---------------------- Page: 16 ----------------------
ISOAEC 9593-3 : 1990 (E)
Abbreviations used in procedure names
Tables
4.1.2 Alphabetical by bound name

This subclause alphabetically lists the Ada procedures corresponding to each PHIGS function. Instances in

which the binding of a name corresponds to more than one PHIGS function indicates the use of Ada

overloading.
ADD NAMES TO SET add names to set
ANNOTATION TEXT RELATIVE annotation text relative
ANNOTATION-TEXT-RELATIVE annotation text relative 3
APPLICATION-DATA- application data
ARCHIVE ALC STRUCTURES archive all structures
ARCHIVE-STRÜCTURE NE’IWORKS archive structure networks
ARCHIVE-STRUCIURES archive structures
AWAIT E%NT await event
BUILD -TRANSFORMATION MATRIX build transformation matrix
BUILD-TRANSFORMATIONSMATRIX build transformation matrix 3
CELL ÄRRAY
cell array
CELL-ARRAY
cell array 3
CHANGE STRUCTURE IDENTIFIER Change structure identifier

CHANGE-STRUCIURE-IDENTIFIER ANDJEFERENCES Change structure identifier and references

CHANGE-STRUCTURE-REFERENCJ?S Change structure references
CLOSE ARCHIVE-FILE- close archive file
CLOSE-PHIGS close PHIGS
CLOSE-STRUCTURE
close structure
CLOSEWS close workstation
COMPÖSE MATRIX compose matrix
COMPOSE-MATRIX
compose matrix 3
COMPOSETRANSFORMATION MATRIX compose transformation matrix
COMPOSE-TRANSFORMATION-MATRIX compose transformation matrix 3
COPY ALL ELEMENTS FROM-STRUCTURE copy all elements from structure
DELETE ALL STRUCI’ÜRES
delete all structures
DELETE-ALL-STRUCIURES FROM-ARCHIVE delete all structures from archive
DELETl-ELEMENT -
delete element
DELETE-ELEMENT RANGE delete element range
DELETE-ELEMENTS BETWEEN-LABELS delete elements between labels
DELETE-STRUCI’URi5 delete structure
DELETE-STRUCI’URE NETWORK delete structure network
DELETE-STRUCIURE-NETWORKS FROM-ARCHIVE delete structure networks from archive
DELETE-STRUCI’URES-FROM-ARCHIVE delete structures from archive
ELEMENT SEARCH element search
EMERGENCY CLOSE PHIGS emergency close PHIGS
EMPTY STRU-CI’URE- empty structure
ERROR-
...

Questions, Comments and Discussion

Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.