Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uunet!stanford.edu!lucid.com!campeau!jwz From: jwz@lucid.com (Jamie Zawinski) Newsgroups: comp.lang.postscript Subject: Re: Alternatives to Adobe's ehandler.ps? Message-ID: Date: 25 Apr 91 19:16:52 GMT References: <9104231442.AA23295@cas.org> <1991Apr24.164156.29515@spool.cs.wisc.edu> <9737@cg-atla.UUCP> Sender: usenet@lucid.com Organization: Lucid, Inc., Menlo Park, CA Lines: 18 In-Reply-To: bradlee@cg-atla.UUCP's message of 25 Apr 91 12:10:41 GMT In article <9737@cg-atla.UUCP> bradlee@cg-atla.UUCP (Rob Bradlee) wrote: > > I'd just like to cast a vote in favor of this error handler. I've used > it for the past year developing several PostScript procsets and it has > been invaluable. By far the best way to debug PostScript is with GhostScript or another on-screen interpreter. Though it's nice that PS gives you the ability to get real error messages out of a piece of printer hardware, that's an incredibly wasteful way to go about it, in terms of both time and trees. (On my Sparc2, GS is about 70 times faster than a laserwriter...) Since GhostScript is free and runs under X11, SunView, and MS-DOS, you really don't have *any* excuse for killing all of those trees... -- Jamie PS: prep.ai.mit.edu:/pub/gnu/ghostscript-2.1.1.tar.Z