| 144 |
|
|
| 145 |
|
The transform command itself is also cumulative, and a transform |
| 146 |
|
command with no arguments is used to return to the previous |
| 147 |
< |
condition. It is best if transforms and their end statements |
| 148 |
< |
("xf" by itself) are balanced in a file, so that later or enclosing |
| 147 |
> |
condition. It is necessary that transforms and their end statements |
| 148 |
> |
("xf" by itself) be balanced in a file, so that later or enclosing |
| 149 |
|
files are not affected. |
| 150 |
|
|
| 151 |
|
Transformations apply only to geometric types, e.g. polygons, spheres, etc. |
| 157 |
|
====== |
| 158 |
|
The -a N transform specification causes the following transform |
| 159 |
|
arguments to be repeated along with the contents of the included |
| 160 |
< |
file N times. (Note that this option is supported only for included |
| 161 |
< |
files.) The first instance of the geometry will be in its initial |
| 162 |
< |
location; the second instance will be repositioned according to the |
| 163 |
< |
named transformation; the third instance will be repositioned by |
| 160 |
> |
objects N times. The first instance of the geometry will be in its |
| 161 |
> |
initial location; the second instance will be repositioned according |
| 162 |
> |
to the named transformation; the third instance will be repositioned by |
| 163 |
|
applying this transformation twice, and so on up to N-1 applications. |
| 164 |
|
|
| 165 |
|
Multi-dimensional arrays may be specified with a single include |
