...More of document prolog and setup...
%%BeginDocument: GRAPHIC.EPS
...Document prolog and setup for EPS file...
/proc1 {
% Enter deferred execution mode
/x exch def
x 4 moveto
} bind def
% x associated with lineto after bind
4 proc1
% Execute proc1 and cause error
...Rest of EPS file...
%%EndDocument
...Rest of including application document...
In the following example, the EPS file
correctly
initializes the variable
x
before defining the procedure
proc1
:
%!PS-Adobe-3.0
...Document prolog of including application...
/x /lineto load def
% Application defines x to be lineto
...More of document prolog and setup...
%%BeginDocument: GRAPHIC.EPS
...Document prolog and setup for EPS file...
/x 0 def
% Initialize variables
before
defining procs
/proc1 {
/x exch def
x 4 moveto
} bind def
4 proc1
% Execute Proc1
...Rest of EPS file...
%%EndDocument
...Rest of including application document...
2.8
Ensuring Portability
Although using outside resources, such as fonts, patterns, files, and procsets,
is allowed in an EPS file, the most portable files are those that are self-
contained and do not rely on outside resources. For example, if an EPS file
requires an encoding other than the default encoding for a font, then the EPS
file should perform the re-encoding.
EPS files must never rely on procedures that are defined in application- or
driver-provided prologs, such as procedures defined in the Apple LaserPrep
file. Such definitions might or might not be present, depending on the actions
of the enclosing program or previous jobs.
Because EPS files should be portable across heterogenous environments,
7-bit ASCII is the recommended format for data in EPS files. Although
binary data is allowed, use caution when producing data that is expected to
be portable. The use of binary data may make it impossible to print on some
printers across some communication channels. Binary data that has special
12
(1 May 92)