Article View: comp.lang.postscript
Article #485Re: Lisp dialect as front end to PostScript
From: Dick Dunn
Date: Sun, 12 Apr 1992 18:33
Date: Sun, 12 Apr 1992 18:33
21 lines
1436 bytes
1436 bytes
barmar@think.com (Barry Margolin) writes: ... >The nice thing is that Lisp and PS have many features in common, so the >mapping can be pretty straightforward. Specifically, they both have >manifest typing... ^^^^^^^^should be "latent"; just a thinko, I assume. >...and dynamic allocation with garbage collection. The latter >is often the hardest part of any Lisp implementation, but the implementor >of this translator wouldn't have to worry about it. Level 1 PostScript interpreters didn't have garbage collection...that's why the save/restore ritual mattered so much. There's nothing to say that they *couldn't* have had garbage collection, but just that none of them [as far as I know] *did* have it. Even in Level 2, it's not clear that the garbage collectors will be capable of compaction. This might make a difference in LISP-like memory usage. -- Dick Dunn rcd@raven.eklektix.com -or- raven!rcd Boulder, Colorado ...Simpler is better.
Technical Details
Message-ID:
<1992Apr12.183304@eklektix.com>Path:
arc1-ca.pugleaf.net!sparky!uunet!cs.utexas.edu!hellgate.utah.edu!csn!raven!rcdReferences:
<1992Apr6.220502.12960@adobe.com> <1992Apr7.014813.1249@cs.yale.edu> <ku3ju9INNqfo@early-bird.think.com>Show Full Headers
Complete Article Headers
Newsgroups: comp.lang.postscript Path: arc1-ca.pugleaf.net!sparky!uunet!cs.utexas.edu!hellgate.utah.edu!csn!raven!rcd From: rcd@raven.eklektix.com (Dick Dunn) Subject: Re: Lisp dialect as front end to PostScript Message-ID: <1992Apr12.183304@eklektix.com> Organization: eklektix - Boulder, Colorado References: <1992Apr6.220502.12960@adobe.com> <1992Apr7.014813.1249@cs.yale.edu> <ku3ju9INNqfo@early-bird.think.com> Date: Sun, 12 Apr 1992 18:33:04 GMT Lines: 21