Information processing systems — Computer graphics — Programmer's Hierarchical Interactive Graphics System (PHIGS) language bindings — Part 1: FORTRAN

Systèmes de traitement de l'information — Infographie — Interfaces langage entre un programme d'application et son support graphique — Partie 1: FORTRAN

General Information

Status
Published
Publication Date
19-Jun-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-1:1990 - Information processing systems -- Computer graphics -- Programmer's Hierarchical Interactive Graphics System (PHIGS) language bindings
English language
213 pages
sale 15% off
Preview
sale 15% off
Preview

Standards Content (sample)

INTERNATIONAL ISO/IEC
STANDARD
95934
First edi tion
1990-06-0 1
Information processing Systems - Computer
graphics - Programmer’s Hierarchical
Interactive Graphits System (PHIGS) language
bindings -
Part 1:
FORTRAN
Systemes de fraifemenf de I’informafion - Infographie - Inferfaces
langage enfre un Programme d’applicafion et son supporf graphique -
Partie 1: FORTRAN
- -
= =
= =
= =
= =
= z
= =
- Reference number
z 4EiiiiF
ISO/IEC 9593-1:199O(E)
----- -----
---------------------- Page: 1 ----------------------
ISO/IEC 95934:1990(E)
Page
Contents

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

Introduction

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

1 Scope

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

2 Normative references

3 Principles ...............................................................................................................

3.1 Specification ......................................................................................................

................................ 2
3.2 Mapping of’PHIGS function names to FORTRAN subroutine names

3.3 Parameters ........................................................................................................

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

3.4 The FORTRAN subset

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

3.5 Error handling
.......................................................................
4 Generating FORTRAN subroutine names

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

5 Data types

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

6 Enumeration types
...............................................................................
7 List of the PHIGS function names
............................................... 24
7.1 List of functions ordered alphabetically by bound name
................................... 29
7.2 List of functions ordered alphabetically by PHIGS function name
............................................................
8 PHIGS errors specific to the FORTRAN binding

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

9 The PHIGS function interface

9.1 General principles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . ..*..........................................................*.....

9.2 Control functions

..*..........................*......................................................

’ 9.3 Output primitive functions

. . . . . ..*.....................................................................

9.4 Attribute specification functions

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

9.4.1 Bundled attribute selection
‘~~..........................................................................
9.4.2 Individual attribute selection

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ..*...........

9.4.3 Aspect Source flag setting

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ..*............................

9.4.4 Workstation attribute table definition

. . . . . . . . . . . . . . . . . . ..*.......................................................

9.4.5 Workstation filter definition

9.4.6 Colour model control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

9.4.7 HLHSR attributes ,......................................................*.................................

9.5 Transformation functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

9.5.1 Modelling transformations . . . . . . ..*..............................................................*.......

9.5.2 View operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ..~.................................

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ..*......

9.5.3 Workstation transformation

. . . . . . . . . . . . . . . . . . . . . ..*.........................~.............. 57

9.5.4 Utility functions to support modelling

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ..~~**~~..**.................

9.5.5 Utility functions to support viewing

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

9.6 Structure content functions

. . . . . . . . . . . . . . . . . . . . . . . . . . ..*...............................................

9.7 Structure manipulation functions
0 lSO/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, wlthout

Permission in writing from the publisher.
ISOAEC Copyright Office l Case Postale 56 l CH-1211 Geneve 20 l Switzerland
Printed in Switzerland
---------------------- Page: 2 ----------------------
Iso/IEC 9593=1:1990(E)

9.8 Structure display functions .....................................................................................

9.9 Structure archiving functions .................................................................................

9.10 Input functions ................................................................................................

910.1 Pick related structure elements .......................................................................

9.10.2 Initialization of input devices ..........................................................................

9.10.3 Setting mode of input devices .........................................................................

9.10.4 Request input functions

................................................................................ 89

9.10.5 Sample input. functions ................................................................................. 92

9.10.6 Event input functions ................................................................................... 95

9.11 Metafile functions .............................................................................................

9.12 Inquiry functions ............................................................................................ 100

9.12.1 Inquiry functions for operating state value ........................................................ 100

9.12.2 Inquiry functions for PHIGS description table ...................................................

100
.............................................................. 102
9.12.3 Inquiry functions for PHIGS state list
........................................................ 104
9.12.4 I.nquiry functions for workstation state list
.............................................. 123
9.12.5 Inquiry functions for workstation description table
............................................................ 144
9.12.6 Inquiry functions for structure state 1%
............................................................. 144
9.12.7 Inquiry functions for structure content
........................................................
9.12.8 Inquiry function for PHIGS error state I’ist 169

.................................................................................................. 171

9.13 Error control

............................................................................................ 172

9.14 Special interfaces

Utility functions not defined in PHIGS ...................................................................... 173

Annexes

............................................................................................ 175

A FORTRAN Examples

....................................................................................................... 200

B Function Lists
........................................... 200
B.1 List of functions ordered alphabetically by function name
............................................. 206
B.2 List of functions ordered alphabetically by bound name
---------------------- Page: 3 ----------------------
ISO/IEC 95934:1990(E)
Foreword
ISO (the International Organization for Standardization) and IEC (the
International Electrotechnical Commission) form the specialized System
for worldwide standardization. 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 com-
mittees collaborate in fields of mutual interest. Other international or-
ganizations, governmental and non-governmental, in liaison with ISO
and IEC, also take patt 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 bod-
ies for voting. Publication as an International Standard requires ap-
proval by at least 75 % of the national bodies casting a vote.
International Standard ISO/IEC 9593-1 was prepared by Joint Technical
Committee ISO/IEC JTC 1, Information technology.
ISOIIEC 9593 consists of the following Parts, under the general title In-
formation processing Systems - Computer graphics - Programmer’s
Hierarchical Interactive Graphits System (PHIGS) language bindings :
- Part i: FORTRAN
- Part 2: Extended Pascal
- Part3: ADA
- Part 4: C
Annex B forms an integral part of this part of ISO/IEC 9593. Annex A is
for information only.
---------------------- Page: 4 ----------------------
BSO/IEC 9593=1:1990(E)
Introduction
The Programmer’s Hierarchical Interactive Graphits System (PHIGS),
the functional description of which is given in ISO/IEC 95924, is speci-
fied 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
for the FORTRAN Computer programming language.
---------------------- Page: 5 ----------------------
This page intentionally left blank
---------------------- Page: 6 ----------------------
ISOIIEC 9593=1:1990(E)
INTERNATIONAL STANDARD
Information processing Systems - Computer graphics -
Programmer’s Hierarchical Interactive Graphits System
(PHIGS) language bindings -
Part 1:
FORTRAN
1 Scope

ISO/IEC 95924 specifies a language independent nucleus of a graphics System. For integration into a pro-

gramming language, PHIGS is embedded in a language dependent layer obeying the particular conven-

tions of that language. This part of ISO/lEC 9593 specifies such a language dependent layer for the FOR-

TRAN language.
2 Normative references

The following Standards contain provisions which, through reference in this text, constitute provisions of

this part of ISODEC 9593. At the time of publication, the editions indicated were valid. All Standards

are subject to revision, and Parties to agreements based on this part of ISO/lEC 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 1539 : 1980, Information processing systems - Programming Languages - FORTRAN.

ISOIIEC 95924 : 1989, Information processing Systems - Computer graphics - Programmer? Hierarhical

Interactive Graphits System (PHIGS) - Part 1 - functional description.

ISO/IEC TR 9973 : 1988, Information processing - Procedures for registration of graphical items.

---------------------- Page: 7 ----------------------
ISO/IEC 95934:1990(E)
3 Principles
3.1 Specification

This part of ISO/IEC 9593 defines the PHIGS language binding interface for FORTRAN 77, as described

in ISO 1539 : 1980. With some minor modifications, application programs tan be transported between full

FORTRAN 77 and FORTRAN 77 Subset PHIGS installations.
3.2 Mapping sf PHIGS function names to FORTRAN subroutine names

The function names of PHIGS are all mapped to FORTRAN subroutine names that Start with the letter

‘P’. The mapping is generally done in a one-to-one correspondence to functions defined in ISO/IEC

9592-1. However, some functions are Split into more than one subroutine in this binding, due to the

The remaining letters after the first one are obtained by deriving a
number of Parameters required.
OPEN becomes OP, WORKSTATION
unique acronym from the words of the function name; e.g.,

becomes WK. Hence, the FORTRAN subroutine name of PHIGS function OPEN WORKSTATION is

POPWK. For a list of all abbreviations, see clause 4. Names used internally that may be known outside

PHIGS, e.g., during linking, Start with some easily recognized and documented form such as ‘PH’ (sub-

routine, function, and comrnon block names). Therefore, no external names starting with this construct

should be Chosen when using PHIGS, in Order to avoid name conflicts.
3.3 Parameters

In general, the Order of PHIGS function Parameters is preserved. For some subroutines, however, there

are additional Parameters that have been inserted in the normal Parameter sequence (e.g., array length

for arrays).

Values of input Parameters are unaltered by any PHIGS function as well as PACK DATA RECORD

and UNPACK DATA RECORD.

In Order that any element of a list (member of a Set), such as the set of structure names, tan be inquired,

in this binding the inquiry functions retum only a Single element of a list (member of a Set). In addition,

the total number of elements of the list (members of the set) is always returned. The elements (members)

are numbered starting from 1; each invocation of the inquiry function requires the desired element

(member) number as aninput Parameter and retums the corresponding element (member). When the

list (Set) is empty, a zero is retumed as the number of elements (members) and the Parameter represent-

ing the Single element (member) in the list is undefined.
3.4 The FORTRAN subset

The binding for FORTRAN 77 Subset is different from that for full FORTRAN 77 in Order to accommo-

date the FORTRAN 77 Subset restrictions.

Those PHIGS subroutines in the full FORTRAN 77 binding that have arguments of type CHARAC-

TER*(*) have alternative subroutine definitions that include fixed length Character strings, CHARAC-

TER”80, for the Subset.

In some cases an additional INTEGER Parameter (the number of characters) appears in the Parameter

list. and the Subset version is distinguished by the addition of a final ‘S’, so that they tan coexist in the

same implementation. In other cases the INTEGER is already present and the FORTRAN 77 Subset

version has the same name as the full FORTRAN 77 Version.
---------------------- Page: 8 ----------------------
ISO/lEC 95934:1990(E)
The FORTRAN subset
Principles

A full FORTRAN 77 implementation shall include both subroutines when the names are distinct and

only the full FORTRAN 77 version when the names are the Same.

The enumeration values in this binding may be redefined by replacing the PARAMETER Statements

with corresponding DATA Statements.
3.5 Error handling

There are two error routines in every PHIGS System, named PERLOG and PERHND. The user may

replace the latter with his/her own subroutine using the same name, PERFIND, and calling sequence.

Furthermore, this user-defined error routine may cal1 the system-defined error logging procedure PER-

LOG.
---------------------- Page: 9 ----------------------
ISOIIEC 9593=1:1990(E)
4 Generating FORTRAN subroutine names

For the binding of the PHIGS functions that inquire lists (Sets), the word ‘element’ (‘member’) is added

to the PHIGS name.

The derivation of the abbreviation for the subroutine names is performed in several Steps. First, plurals

are reduced to their Singular ferm,’ and then compound terms are reduced to maintain uniqueness and

appropriate name length. Finally, each remaining word is replaced by the null string or by an abbrevia-

tion.
Table 1 - Reduction of Plurals to Singulars
DEVICES
DEVICE
ELEMENTS
ELEMENT
EVENTS
EVENT
FILE-S
FILE
IDENTIFIERS
IDENTIFIER
INDICES
INDEX
LABELS
LABEL
LENGTHS
LENGTH
NETWORKS
NETWORK
PATHS
PATH
IWMITNE
PRI0RITIFS PRIORITY
REFERENCES REFERENCE
TRANSFORMATIONS
TRANSFORMATION
STRUCTURES
STRUCIURE
mEs TYPE
WORKSTATIONS
WORKSTATION
---------------------- Page: 10 ----------------------
ISOIIEC 9593=1:1990(E)
Generatirng FORTRAN subroutine names
Table 2 - Reduce compound terms for uniqueness
ANNOTATION TEXT CHARACTER HEIGHT ATCH
ANNOTATION TEXT CHARACTER UP ATCU
INQUIRE ANNOTATION TEXT
QAT
SET ANNOTATION TEXT SAT
ANNOTATION TEXT RELATIVE ATR
ARCHIVE ALL ARA
ARCHIVE STRUCTURE IDENTIFIER ASID
IDENTIFIER AND REFERENCE
CSTID
CHANGE STRUCTURE IDENTIFIER
DELETE ALL STRUCIURE DAS
DSTR
DYNAMICS OF STRUCTURE
DYNAMICS OF WORKSTATION A’ITR.IBUTES DSWA
EDGE FLAG EDFG
ELEMENT POINTER EP
ELEMENT CONTENT EC0
ELEMENT TYPE AND SIZE ETS
ERROR HANDLING MODE ERHM
EVALUATE VIEW MAPPING MATRIX EVMM
EVALUATE VIEW ORIENTATION MATRIX EVOM
GENERALIZED STRUCTURE ELEMENT GSE
INDIVIDUAL ASF IASF
LIST OF
E AVAILABLE GENERALIZED DRAWING PRIMITIVE 3 EGD3
MAXIMUM LENGTH
--P
MODELLING CLIPPING VOLUME MCV
MODELLING CLIPPING MCL
PRPV
PATTERN REFERENCE POINT AND VECTORS
PATTERN REFERENCE POINT PARF
--P
RETRIEVE ALL RA
RETRIEVE STRUCTURE IDENTIFIER RSID
SET OF element
STRUCTURE IDENTIFIER SID
STRUCTURE PATH ’ STPA
STRUCTURE NETWORK -, SN
STRUCTURE STATE .+ STRS
TEXT FONT -+ TXFN
-+ TP
TRANSFORM POINT
-,’ U-PA
UNPOST ALL
+ VT
VIEW TRANSFORMATION
+ WKST
WORKSTATION STATE VALUE
(FORTRAN 77 subset) -, s
---------------------- Page: 11 ----------------------
ISOIIEC 9593=1:1990(E)
Generating FORTRAN subroutine names
Table 3 - Deletions
element ALL AT AVAILABLE
BETWEEN DATA DEVICE FACTOR
EVENT
FROM IN
LIST METAFILE MORE
NAME!3 NUMBER OF SIZE SUPPORTED
TABLE TO TYPE VALUE VECTOR
WHICH
Table 4 - Abbreviations
3 + 3 EMPTY --+ EM
ADD + AD ERROR -+ ER
ALIGNMENT -, AL ESCAPE -+ Esc
ANCESTORS + AN EVALUATE -+ EV
ANNOTATION -, AN EXECUTE -, EX
APPLICATION -+ AP EXPANSION -+ XP
ARCHIVE + AR EXTENT 3 x
AREA
-+ A FACILITIES + F
ARRAY
-, A FILE -+ F
ASF -+ ASF FILL -+ F
AWAIT -* WAIT FILTER + Fr
BUILD + BL FLAG . + F
CATEGORY + CA FLUSH + FLUSH
CELL + c FONT -+ F
CHANGE + c GENERALIZED + G
CHARACTER + CH GET + GT
CHOICE -+ CH GLOBAL -+ GM
CLASSIFICATION -, CL HANDLING -+ HND
CLOSE -+ CL HEIGHT -+ H
COLOUR + c HIGHLIGHTING + HL
COMPOSE + CO HLHSR 3 HR
CONFLICT + CN IDENTIFIER + ID
CONFLICTING + C INCREMENTAL -, 1
CONNECTION + C INDEX + 1
CONTENT INDICATOR -+ 1
+ CT
INDIVIDUAL + 1
COPY i -+ c
CURRENT INITIALIZE + IN
+ c
DEFAULT -, D INPUT -, 1
DESCENDANTS -, DE INQUIRE
DELETE + D INTERPRET -+ 1
DISPLAY -+ D INTERIOR + 1
DRAWING + D INVISIBILITY -+ IV
EDGE + ED ITEM 3 ITM
EDGETYPE + EDT LABEL + LB
EDGEWIDTH -+ EW LENGTH + L
EDIT + ED LINETYPE 3 LN
ELEMENT + EL LINEWIDTH -+ LW
EMERGENCY + E LOCAL -, LM
---------------------- Page: 12 ----------------------
ISOIIEC 95934:1990(E)
Generating FORTRAN subroutine names
Table 4 (continued) - Abbreviations
LOCATOR + LC RESOLUTION -+ RS
LOGGING -, LOG RESTORE -+ R
LOGICAL -* L RETRIEVE -* RE
MAPPING -+ MP ROTATE -+ RO
MARKER + MK SAMPLE -* SM
+ M SCALE -+ sc
MATRIX
-* MSG SEARCH + s
MESSAGE
-, M SET + s
MODE
SIMULTANEOUS -* SIM
MODEL -+ MD
NETWORK -, N SPACE -+ SP
SPACING
OFFSET + OS + SP
OPEN -+ OP SPATIAL + s
ORIENTATION -+ OR STATE -+ s
OVERFLOW + ov STATUS -* ST
PACK -+ P STRING + ST
PATH -+ P STROKE -* SK
PATTERN -+ PA STRUCTURE -+ ST
PHIGS -* PH STYLE -* s
PICK -+ PK SYSTEM 3 SY
POINTER -+ PT TEXT -* TX
-+ PL TRANSFORM -+ T
POLYLINE
POLYMARKER -+ PM TRANSFORMATION -, T
TRANSLATE -+ TR
POST -+ PO
UNPACK + u
POSTED -+ PO
UNPOST + UPO
PRECISION -+ PR
PREDEFINED -+ P UP + UP
UPDATE
PRIMITIVE -+ P + u
-+ VL
PRIORITY + P VALUATOR
VIEW -+ VW
QU=J-E + Q
RANGE + RA VIEWPORT + v
READ -+ RD VOLUME + VOL
RECORD + REC WINDOW -+ w
REDRAW -+ R WRITE 3 w
REFERENCE -, RF WORKSTATION -* WK
REMOVE + RE’ X -, x
REPRESENTATION + R ‘Y -+ Y
Z -+ z
REQUEST + RQ
---------------------- Page: 13 ----------------------
IEC 95934:1990(E)
5 Data types

In ISO/IEC 9592-1 Parameters of several types are used. The following Shows the correspondence

between the types used in ISO/IEC 9592-1 and their realization in a FORTRAN implementation.

PHIGS Data Type FORTRAN Data Types
1 integer INTEGER

A(1) array of integers This is described more at the end of this clause, where the representations of

CELL ARRAY and PATTERN are described.
R real REAL
const x simple-type where simple-type is realized as 1 or R
(vector of values, for example 2~ R)
For input argument where const 26 or for output argument where const ~4,
then array of constant length is used, otherwise use separate Parameters.
x const 2 x R (matrix‘of values, for example 2~ 3~ R)
const 1
REAL array (const 1, const 2)
For example, in Order to store the projection transformation defined by:
x --cr’
y + y’/w’
z + Zl /W
in a 4 x 4 x REAL matrix, the values shall be stored such that:
XI = p[l,l]“x + p[2,l]“y + p[3,l]“z + p[4,1]
VI = p[1,2] *x + p[2,2]“y + p[3,2]*z + p[4,2]
Zl = p[1,3]*x + p[2,3]*y + p[3,3]“z + p[4,3] .
w’ =
p[1,4]“x + p[2,4]“y + p[3,4]“z + p[4,4]
S string 1) In a full FORTRAN 77 subroutine:
a) INTEGER containing the number of characters returned (for output
string argument only) .
b) CHARACTER*(*) containing the string. In addition, if a Character
string that is an input Parameter may reasonably contain no characters,
then an INTEGER (20) is used to give the number of characters to be
passed to the subroutine.
2) In a FORTRAN 77 Subset subroutine:
a) INTEGER containing thk number of characters passed to the subrou-
tine (for input string only, i.e. only one INTEGER needed for output).
b) INTEGER containing the number of characters retumed (for output
string argument only). If the value is < 0 or > 80, error 2004 is
---------------------- Page: 14 ----------------------
ISO/IEC 95934:1990(E)
Data types
generated.
c) CHARACTER*80 containing the string.
P2 Point REAL, REAL containing the X- and Y-values
const X P2 (only occurs in non-inquiry functions)
Separate REAL Parameters, with the X- and Y- coordinates of one Point
being followed by the X- and Y- coordinates of the next.
P3 Point REAL, REAL, REAL containing the X-, Y-, and Z-values

const X P3 If const 22 REAL arrays xa(const), ya(const), za(const) are used, otherwise

separate REAL arrays are used, with the X-, Y-, and Z-coordinates of one
Point being followed by the X-,Y-, and Z-coordinates of the next.
L(L(P2/3)) list of Point lists (for fill area Sets)
The following description applies to both 2D and 3D Point lists except that the
PZA array is not present for 2D Point lists. The arguments that specify the
list of Point lists are as follows:
INTEGER NPL
INTEGER IXA(NPL)
REAL PXA( *), PYA(*), PZA( *)
where
NPL is the number of Point lists
IXA is an array of end indices for the Point lists
PXA, PYA, PZA are the coordinate arrays
The range of indices in PXA, PYA, and PZA of each Point list is as follows:
1 to IXA(l) is the first Point list
IXA(i-1)+1 to IXA(i) is the ith Point list, for i=2, to NPL when NPL 22
Thus, for example:
a) 1 is the Start index for the 1st Point list,
b) IXA(i-l)+ 1 is the Start index for the ith Point list for all i=2 to NPL
when NPL12, and
c) IXA(i) is the end index for all point lists i.= 1 to NPL.

In the actual arguments specifyingthe list of Point lists (supplied by the appli-

cation program), the following conditions shall hold true; otherwise error 2005
is generated, with the allowable exception:
d) NPLzl,
e) PXA, PYA and PZA are dimensioned by at least IXA(NPL) (however
it is allowable for the implementation not to generate error 2005 in this
case) ,
f) IXA(1)13 (the first Point list is at least 3 Points),
g) IXA(i+l)-IXA(i)r3 for i=l to NPL-1, when NPLr2 (the ith Point
list is at least 3 points).
REAL, REAL containing the X- and Y-values specifying an offset from some
V2 2D vector
reference Point ‘in the coordinate System of the reference Point.
---------------------- Page: 15 ----------------------
ISO/IEC 9593~1:3990(E) .
Data types
REAL, REAL, REAL containing the X-, Y-, and Z-values specifying an
V3 3D vector
offset from some reference Point in the coordinate System of the reference
Point.
E enumeration
INTEGER
All values are mapped to the range zero to N-l, where N is the number of
enumeration alternatives. Except for null values, the Order of the enumera-
tion alternatives is the same as in ISO/IEC 95924 : null values always appear
in the first Position. If the integer value given by the application program is
not in the range 0 to N-l, there is a language binding error condition (error
2000).
const x E (only occurrence in PHIGS is const = 18)
An array of INTEGER elements of dimension const is used, each element
being an enumeration alternative.
INTEGER identifying the name sf an element of a name set. The domain of
NM classification
the names is the set of INTEGERS from 0 to an implementation defined
maximum. The minimum maximum is 63.

FR filter A compound data type containing two name Sets representing inclusion and

exclusion Sets. Represented as two Sets. For input Parameter:
INTEGER giving the number of elements in the inclusion set, an array of
INTEGERs giving the elements in the inclusion set, INTEGER giving the
number of elements in the exclusion set, and an array of INTEGERs giv-
ing the elements in the exclusion set.
For output Parameter:
INTEGER (input) giving the dimension (ni) of the array that will contain
INTEGER (input) giving the dimension
the elements of inclusion set.
(ne) of the array that will contain the elements of exclusion set.
INTEGER (output) giving the number of elements of the inclusion set
array actually used. INTEGER (output) giving the number of elements of
the exclusion set array actually used. Array of INTEGERs (output) con-
taining the elements in the inclusion set. Array of INTEGERs (output)
containing the elements in the exclusion set.
If the size required to contain the inclusion or exclusion elements is greater
than the size of the arrays supplied (as determined by the dimensions ni and
ne), error 2001 will be generated and the value returned in the corresponding
INTEGER (output) Parameters will respresent the input array size required.
L(FR) list of filter
This data type is only used in the incremental search functions and applies to
both the “normal” and “inverted” lists of filters. The arguments that specify
the list of filters are as follows:
INTEGER FLN
INTEGER FLISX(FLN)
. INTEGER FLIS(*)
INTEGER FLE!SX(FLN)
INTEGER FLES(“)
where
---------------------- Page: 16 ----------------------
ISOIIEC 95934:1990(E)
Data types
FLN is the number filters
FLISX is an array of end indices of each inclusion set in the list filters
FLIS is the array of elements of the inclusion sets
FLESX is an array of end indices of each exclusion set in the list filters
FLES is the array of elements of the exclusion sets
The range of indices in F’LIS of each inclusion set is as follows:
1 to FLISX(1) is the first inclusion set,
FLISX(i-l)+ 1 to FLISX(i) is the ith inclusion set,
for i=2, to FLN when FLN 22
Correspondingly the range of indices in FLES of each exclusion set is as fol-
lows:
1 to F’LESX(1) is the first exclusion set,
FLESX(i-l)+ 1 to FLESX(i) is the ith exclusion set,
for i=2, to FLN when FLN 22
Thus, for example:
a) 1 is the Start index for the first inclusion set,
b) FLISX(i-l)+ 1 is the Start index for the i’th inclusion set for all i=2 to
FLN when FLNz2, and
c) F’LISX(i) is the end index for all inclusion sets i= 1 to FLN.
In the actual arguments specifying the list filters (supplied by the application
program), the following conditions shall hold true; otherwise error 2006 is
generated, with the allowable exception:
d) FLNrl,
e) FLIS and FLES are dimensioned by at least FLESX(FLN) (however it
is allowable for the implementation not to generate error 2006 in this
case) ,

a set of siinple-type (for example, SET(NM) or SET(E)): INTEGER giving the number of ele-

ments in the set and an array of simple-QW giving the elements in the se
...

Questions, Comments and Discussion

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