Path: utzoo!attcan!uunet!wuarchive!zaphod.mps.ohio-state.edu!swrinde!cs.utexas.edu!execu!sequoia!rpp386!woody
From: woody@rpp386.cactus.org (Woodrow Baker)
Newsgroups: comp.lang.postscript
Subject: Re: PostScript Language
Summary: humph!
Message-ID: <18061@rpp386.cactus.org>
Date: 1 Mar 90 14:38:33 GMT
References: <9465@imagen.UUCP> <1990Mar1.055001.13273@chinet.chi.il.us>
Organization: River Parishes Programming, Plano, TX
Lines: 14

In article <1990Mar1.055001.13273@chinet.chi.il.us>, les@chinet.chi.il.us (Leslie Mikesell) writes:
> It's a pretty safe bet that he doesn't use it in the way that you implied
> (i.e. by typing raw postscript directly at a printers input port) since
> no one in their right mind would do that.  What's wrong with using a computer

First of all, the PS printer does not provide any kind of editor, with the
exception of destructive backspace.  That makes it tough to enter code
directly in executive mode.  In general, I use a editor to do the work.
However, there is no substitte for being able to toggle into executive
and watch and experiment with what things do.  It's the simplest way
to get a complex stack manipulation working.

Cheers
Woody