Article View: comp.lang.postscript
Article #481Re: Lisp dialect as front end to PostScript
From: Gerald Q. Maguire
Date: Sun, 12 Apr 1992 08:21
Date: Sun, 12 Apr 1992 08:21
13 lines
1345 bytes
1345 bytes
One thing which you can do is hand the resulting LISP to one of several code analyzers and find the dependency chains and thus compute each of the chains concurrently. Some analysis which I did 1988 indicates that these chains are typically short and there are a lot per page (for typical output generated by formatters such as SCRIBE) thus there is a lot of potential for parallelism. A side benefit is that you know which characters in which font and what size to cache for subsequent rendering of a page - which is great if you are going to reprint this page later; ideally it allows you to keep multiple representations of a page and emit previous versions very quickly for a given device. Chip
Technical Details
Message-ID:
<MAGUIRE.92Apr12032101@cs.cs.columbia.edu>Path:
arc1-ca.pugleaf.net!sparky!uunet!cs.utexas.edu!usc!sol.ctr.columbia.edu!cs.columbia.edu!maguireReferences:
<1992Apr10.010246.53651@cs.cmu.edu> <1992Apr10.171701.1856@adobe.com>Show Full Headers
Complete Article Headers
Newsgroups: comp.lang.postscript Path: arc1-ca.pugleaf.net!sparky!uunet!cs.utexas.edu!usc!sol.ctr.columbia.edu!cs.columbia.edu!maguire From: maguire@cs.columbia.edu (Gerald Q. Maguire) Subject: Re: Lisp dialect as front end to PostScript In-Reply-To: byer@adobe.com's message of Fri, 10 Apr 1992 17:17:01 GMT Message-ID: <MAGUIRE.92Apr12032101@cs.cs.columbia.edu> Sender: news@cs.columbia.edu (The Daily News) Nntp-Posting-Host: cs.columbia.edu Organization: Columbia University Department of Computer Science References: <1992Apr10.010246.53651@cs.cmu.edu> <1992Apr10.171701.1856@adobe.com> Date: Sun, 12 Apr 1992 08:21:01 GMT Lines: 13