Path: utzoo!utgpu!jarvis.csri.toronto.edu!clyde.concordia.ca!mcgill-vision!bloom-beacon!snorkelwacker!think!zaphod.mps.ohio-state.edu!math.lsa.umich.edu!emv
From: montnaro@spyder.crd.ge.com (Skip Montanaro)
Newsgroups: comp.archives
Subject: [comp.lang.postscript] Re: How do you debug PostScript?
Message-ID: <10801@stag.math.lsa.umich.edu>
Date: 6 Feb 90 23:07:37 GMT
Sender: news@math.lsa.umich.edu
Reply-To: montanaro@crdgw1.ge.com (Skip Montanaro)
Followup-To: comp.lang.postscript
Lines: 22
Approved: emv@math.lsa.umich.edu (Edward Vielmetti)

Archive-name: psiber/29-Jan-90
Original-posting-by: montnaro@spyder.crd.ge.com (Skip Montanaro)
Original-subject: Re: How do you debug PostScript?
Archive-site: tumtum.cs.umd.edu [128.8.128.49]
Reposted-by: emv@math.lsa.umich.edu (Edward Vielmetti)

In article <17801@rpp386.cactus.org> woody@rpp386.cactus.org (Woodrow Baker) writes:

   In article <13991@reed.UUCP>, mojo@reed.UUCP (Jet Pilot) writes:
   > 
   > Well, I have just started learning PostScript, and am curious about how
   > people actually go about developing PS code.

   IF you have a mac, get Lasertalk.

If you have a Sun, get NeWS or X/NeWS, then get Don Hopkins' PSIBER Space
Deck. (PSIBER == PostScript Interactive Bug Eradication Routines.) Available
via anonymous FTP from tumtum.cs.umd.edu, I believe.


--
Skip (montanaro@crdgw1.ge.com)