Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!asuvax!ncar!elroy.jpl.nasa.gov!decwrl!pa.dec.com!e2big.mko.dec.com!engage!3d.enet.dec.com!davis
From: davis@3d.enet.dec.com (Peter Davis)
Newsgroups: comp.lang.postscript
Subject: Re: What is a good pathforall substitute??
Message-ID: <1991May3.181435.16458@engage.enet.dec.com>
Date: 3 May 91 20:09:38 GMT
Sender: news@engage.enet.dec.com (USENET News System)
Organization: Digital Equipment Corporation
Lines: 29


In article <1978@chinacat.Unicom.COM>, woody@chinacat.Unicom.COM (Woody Baker @ Eagle Signal) writes...
>
>Don lancaster published a routine called apathforall in the computer shopper
>several months ago.  It turns out to be a part of the Metamorphisis (sic)
>package from Altsys.  It works by turning off the charpath checking flag.
> 
>This was sent to me by lawrence.  He cleared it for distribution some
>time ago.  It accomplishes the same thing.  It gives you a character path.
>Cheers
>Woody
>

I tried this out on both printer and Display PostScript.  In both interpreters,
it blew up with:

	undefined: Name not known - offending command is cexec

Since I didn't find cexec in the text portion of the file, I assume it's buried
in the eexec encrypted portion.  Is there a readable version of this around? 

Better still, is there a working version?

If there's really a way to unprotect charpath outlines in Level 1 PostScript,
that would be extremely useful.  I'd be surprised if Adobe left such a hole,
though.  How does one access internal flags such as the charpath checking flag?

Thanks.
-pd