semi合集-English.pdf - 第5913页
SEMI P39-0304 E2 © SEMI 2004 16 17.2 propnam e-string is an n-string which holds the pr operty name. The reference-number is an unsigned- integer which is either implicitly or exp licitly assigned to the property na me. …

SEMI P39-0304
E2
© SEMI 2004 15
15 CELLNAME Record
15.1 A CELLNAME record associates the name of a cell with a unique reference number. This allows CELL and
PLACEMENT records, if desired, to avoid redundantly storing the actual text of the cell name and instead refer to
the cell by its assigned reference number. It has the following format:
‘3’ cellname-string
‘4’ cellname-string reference-number
15.2 cellname-string is an n-string which holds the cell name. The reference-number is an unsigned-integer
which is either implicitly or explicitly assigned to the cell. Implicit assignment occurs in record type ‘3’, by
assigning sequential reference numbers beginning with 0 as each successive CELLNAME record is encountered.
Explicit assignment occurs in record type ‘4’.
15.3 Two standard properties, S_BOUNDING_BOX and S_CELL_OFFSET (described in Section A2-2 on page
36), may be associated with each CELLNAME record. When all CELLNAME records have been grouped into a
single contiguous table in strict mode (as described in Section 13 on page 13), with an S_CELL_OFFSET property
for every CELLNAME record, the table forms a complete index of all cells in the OASIS file, suitable for random
access.
15.4 Record types ‘3’ and ‘4’ may not both be used in the same OASIS file.
15.5 EXCEPTION HANDLING
— The appearance of two CELLNAME records in the same file with the same
number but different names, or two CELLNAME records in the same file with the same name but different
numbers, should be treated as a fatal error. The appearance of both record types ‘3’ and ‘4’ in the same OASIS file
should be treated as a fatal error. The presence of more than one S_CELL_OFFSET or S_BOUNDING_BOX
property after a given CELLNAME record should be treated as a fatal error.
16 TEXTSTRING Record
16.1 A TEXTSTRING record associates a text string with a unique reference number. This allows TEXT records,
if desired, to avoid redundantly storing the actual text of the string and instead refer to the string by its assigned
reference number. It has the following format:
‘5’ text-string
‘6’ text-string reference-number
16.2 text-string is an a-string which holds the text string. The reference-number is an unsigned-integer which is
either implicitly or explicitly assigned to the text string. Implicit assignment occurs in record type ‘5’, by assigning
sequential reference numbers beginning with 0 as each successive TEXTSTRING record is encountered. Explicit
assignment occurs in record type ‘6’.
16.3 Record types ‘5’ and ‘6’ may not both be used in the same OASIS file.
16.4 EXCEPTION HANDLING
— The appearance of two TEXTSTRING records in the same file with the same
number but different names, or two TEXTSTRING records in the same file with the same name but different
numbers, should be treated as a fatal error. The appearance of both record types ‘5’ and ‘6’ in the same OASIS file
should be treated as a fatal error.
17 PROPNAME Record
17.1 A PROPNAME record associates the name of a property with a unique reference number. This allows
PROPERTY records, if desired, to avoid redundantly storing the actual text of the property name and instead refer
to the property name by its assigned reference number. It has the following format:
‘7’ propname-string
‘8’ propname-string reference-number

SEMI P39-0304
E2
© SEMI 2004 16
17.2 propname-string is an n-string which holds the property name. The reference-number is an unsigned-
integer which is either implicitly or explicitly assigned to the property name. Implicit assignment occurs in record
type ‘7’, by assigning sequential reference numbers beginning with 0 as each successive PROPNAME record is
encountered. Explicit assignment occurs in record type ‘8’.
17.3 Record types ‘7’ and ‘8’ may not both be used in the same OASIS file.
17.4 EXCEPTION HANDLING
— The appearance of two PROPNAME records in the same file with the same
number but different names, or two PROPNAME records in the same file with the same name but different
numbers, should be treated as a fatal error. The appearance of both record types ‘7’ and ‘8’ in the same OASIS file
should be treated as a fatal error.
18 PROPSTRING Record
18.1 A PROPSTRING record associates a property string with a unique reference number. This allows
PROPERTY records, if desired, to avoid redundantly storing the actual text of the property string and instead refer
to the property string by its assigned reference number. It has the following format:
‘9’ prop-string
‘10’ prop-string reference-number
18.2 prop-string is an a-string, b-string , or n-string which holds the property string, depending on the referencing
PROPERTY record. The reference-number is an unsigned-integer which is either implicitly or explicitly assigned
to the property string. Implicit assignment occurs in record type ‘9’, by assigning sequential reference numbers
beginning with 0 as each successive PROPSTRING record is encountered. Explicit assignment occurs in record
type ‘10’.
18.3 Record types ‘9’ and ‘10’ may not both be used in the same OASIS file.
18.4 EXCEPTION HANDLING
— The appearance of two PROPSTRING records in the same file with the same
number but different names should be treated as a fatal error. The appearance of both record types ‘9’ and ‘10’ in the
same OASIS file should be treated as a fatal error.
19 LAYERNAME Record
19.1 A LAYERNAME record provides a means of mapping numeric (layer,datatype) and (layer,texttype)
combinations to layer names. It has the following format:
‘11’ layername-string layer-interval datatype-interval
‘12’ layername-string textlayer-interval texttype-interval
19.2 Record type ‘11’ maps a range of (layer,datatype) numbers to a layer name, and record type ‘12’ maps a range
of (textlayer,texttype) numbers to a layer name.
19.3 layername-string is an n-string containing the layer name.
19.4 Each of the interval fields consists of an unsigned-integer denoting the interval type, followed by 0, 1, or 2
unsigned-integers representing the bounds of that interval as follows:
Table 13 LAYERNAME Interval Types
Type Bounds Implied Range
0
0 to
1
bound-a
0 to bound-a
2
bound-a
bound-a to
3
bound-a bound-a
4
bound-a bound-b
bound-a to bound-b

SEMI P39-0304
E2
© SEMI 2004 17
19.5 LAYERNAME records may be repeated for the same layer name. The complete mapping for a layer name is
formed by the union of all layer, datatype, textlayer, and texttype ranges associated with that name.
20 CELL Record
20.1 A CELL record introduces a cell definition. It has the following format:
‘13’ reference-number
‘14’ cellname-string
20.2 In record type ‘13’, reference-number is an unsigned-integer referring to a CELLNAME record where the
cell name is stored. In record type ‘14’, cellname-string stores the cell name locally. In either representation, the
cell name must be an n-string.
20.3 All subsequent records in the file up to the next CELL, END, or <name> record are considered to be part of
that cell.
20.4 EXCEPTION HANDLING
— Use of a reference-number for which there is no corresponding CELLNAME
record within the same OASIS file should be treated as a fatal error. Multiple CELL records within a single file
which refer to the same cell name (in effect, a duplicate cell definition) should also be treated as a fatal error.
21 XYABSOLUTE & XYRELATIVE Records
21.1 The XYABSOLUTE and XYRELATIVE records control the value of modal variable xy-mode, which in turn
governs the interpretation of the x and y values found in PLACEMENT, <geometry>, and TEXT records. They
consist simply of a record-ID with no additional fields:
‘15’ = XYABSOLUTE
‘16’ = XYRELATIVE
21.2 When each CELL record is encountered, modal variable xy-mode is set to absolute, and related modal position
variables placement-x, placement-y, geometry-x, geometry-y, text-x, and text-y are set to 0. The presence of an
XYRELATIVE record forces modal variable xy-mode to relative, and the presence of an XYABSOLUTE record
forces modal variable xy-mode to absolute. This mode may be changed any number of times within a cell definition.
21.3 In absolute mode, explicit x and y values, when present, are used directly as the actual (x,y) coordinates.
21.4 In relative mode, explicit x and y values, when present, are interpreted as relative displacements from the
stored position information in modal variables placement-x, placement-y, geometry-x,
geometry-y, text-x, or text-y,
depending on the record type in which they occur. In this mode, the actual x-coordinate is computed as the sum of
the x value and its corresponding modal position variable, and the actual y-coordinate is computed as the sum of the
y value and its corresponding modal position variable.
21.5 In both absolute and relative modes, when an x or y value is not explicitly present in the record, the value of
the corresponding modal position variable is used for the actual x or y coordinate. In both absolute and relative
modes, the corresponding modal position variables are always updated with the actual (x,y) coordinate position.
21.6 The interpretation of point-lists and repetitions does not depend on absolute or relative mode. Also, even when
a given element includes a repetition, the corresponding modal position variables (placement-x, placement-y,
geometry-x, geometry-y, text-x, or text-y) are always updated with the actual (x,y) coordinate of the initial element.
22 PLACEMENT Record
22.1 A PLACEMENT record describes one or more placements of the referenced cell within the current cell. It has
the following format:
‘17’ placement-info-byte [ reference-number | cellname-string ] [ x ] [ y ] [ repetition ]
‘18’ placement-info-byte [ reference-number | cellname-string ] [ magnification ] [ angle ]
[ x ] [ y ] [ repetition ]