Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!usc!cs.utexas.edu!chinacat!woody
From: woody@chinacat.Unicom.COM (Woody Baker @ Eagle Signal)
Newsgroups: comp.lang.postscript
Subject: Re: Esoterica
Summary: The Black Book
Message-ID: <1950@chinacat.Unicom.COM>
Date: 18 Apr 91 03:44:52 GMT
References: <91106.223204CXT105@psuvm.psu.edu>
Organization: a guest of Unicom Systems Development, Austin
Lines: 16

In article <91106.223204CXT105@psuvm.psu.edu>, CXT105@psuvm.psu.edu (Christopher Tate) writes:
> ErodeSW, CCRun, xlck, or ylck do?
> 
The Type 1 Font book (the Black Book) explains most of these details.
it does not cover superexec.  Superexec is just like exec, except that it
bypasses a majority of the invalid access errors.  The simplest way
to use it is to enclose a sequence of operations in { } and feed that
to superexec.  Nearly everything that will raise an invalid access error
will work.
> 
> -------
> Christopher Tate                   | "Excuse me, is this your bag?"
>                                    | "No."
> cxt105@psuvm.psu.edu               | "Are you sure?  Do take your time."
> {...}!psuvax1!psuvm.bitnet!cxt105  | "This is definitely *not* my bag."
> cxt105@psuvm.bitnet                | "Just as we thought...."