Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!zaphod.mps.ohio-state.edu!sol.ctr.columbia.edu!cica!iuvax!purdue!decwrl!adobe!heaven!glenn
From: glenn@heaven.woodside.ca.us (Glenn Reid)
Newsgroups: comp.lang.postscript
Subject: Re: EPS and array packing mode
Keywords: EPS, packing
Message-ID: <169@heaven.woodside.ca.us>
Date: 9 Apr 90 03:12:35 GMT
References: <1813@gannet.cl.cam.ac.uk> <1832@gannet.cl.cam.ac.uk>
Reply-To: glenn@heaven.UUCP (Glenn Reid)
Organization: Skyline Press, Woodside CA
Lines: 34

In article <1832@gannet.cl.cam.ac.uk> cet1@cl.cam.ac.uk (C.E. Thompson) writes:
>Two weeks ago, in article <1813@gannet.cl.cam.ac.uk>, I wrote 
>>
>>Can an EPS file assume a particular value for 'currentpacking', or should
>>it set the value if necessary? Conversely, must it restore the value if it
>>changes it? There doesn't seem to be anything explicit in the Adobe
>>documentation about this.

An EPS file should be able to assume that 'currentpacking' is 'false', since
things can break if it isn't (like writing into an array).  The host program
should definitely restore the packing before it includes an EPS file.

But, I would recommend setting it to what you want, and returning it to what
it was before you started.  It's pretty easy, and provides the maximum
amount of protection for both you and your surrounding environment.  This
is generally the right idea for anything resembling EPS; leave the
environment as you found it, and 

/currentpacking where { %if
    pop % dictionary from "where" operator
    /pack currentpacking def
    true setpacking
} if

% your stuff here

/setpacking where { %if
    pop
    pack setpacking
} if


/Glenn
pop