Path: utzoo!utgpu!jarvis.csri.toronto.edu!clyde.concordia.ca!uunet!intercon!news
From: amanda@mermaid.intercon.com (Amanda Walker)
Newsgroups: comp.lang.postscript
Subject: Re: Printer state between pages
Message-ID: <1708@intercon.com>
Date: 10 Jan 90 02:22:46 GMT
References: <1990Jan8.195614.27489@Neon.Stanford.EDU> <17604@rpp386.cactus.org> <1699@intercon.com> <1596@adobe.UUCP>
Sender: news@intercon.com
Reply-To: amanda@mermaid.intercon.com (Amanda Walker)
Lines: 16

In article <1596@adobe.UUCP>, gelphman@adobe.COM (David Gelphman) writes:
> Basically a user path is a procedure which contains
> pure path construction (with optional caching) and can be passed directly
> to operators like 'ustroke' and 'ufill' to stroke and fill a user path.
> You can keep these objects around like normal procedure bodies and repeatedly
> fill and/or stroke them.

Now, this is what I was hoping to hear :-).  Any plans to retrofit this
into "hardcopy PostScript"?  I like the caching part particularly.  Looks
like it's time for to read up on Display PostScript.

Now if only I could buy it for a Macintosh :-)...

Amanda Walker
InterCon Systems Corporation
--