Debugging Postscript

Article View: comp.lang.postscript

Article #8155

Back to comp.lang.postscript Previous Next

#8155

From: Gary D. Wong
Date: Sat, 25 Mar 1989 00:34

14 lines
1271 bytes

Good morning netland. Being new to the postscript world, I am continually
amazed with the capabilities of this language. But one point has continued
to bother me. Can anyone suggest a good method of finding errors in 
postscript files?  It seems to me that the only way to know if an error
exists is if the file does not print. Besides using the interactive mode,
does PS have any type of feedback that might lead to the soruce of the error?
Thanks for the help.



 Gary D. Wong  gar@cory.berkeley.edu  //   "It is better to remain silent   \\
 University of California, Berkeley   <<    and thought a fool, than to     >> 
 (415) 642-9304		              \\    open your mouth and confirm it" //
 Disclaimer: "Really Colonel Hogan, I see NOTHING, I see NOOOTHINNNNNG!"

Technical Details

Message-ID: <11401@pasteur.Berkeley.EDU>

Path:

arc1-ca.pugleaf.net!utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!ucbvax!pasteur!cory.Berkeley.EDU!gar

Show Full Headers

Complete Article Headers

Path: arc1-ca.pugleaf.net!utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!ucbvax!pasteur!cory.Berkeley.EDU!gar
From: gar@cory.Berkeley.EDU (Gary D. Wong)
Newsgroups: comp.lang.postscript
Subject: Debugging Postscript
Keywords: Errors, Debugging.
Message-ID: <11401@pasteur.Berkeley.EDU>
Date: 25 Mar 89 00:34:23 GMT
Sender: news@pasteur.Berkeley.EDU
Reply-To: gar@cory.Berkeley.EDU (Gary D. Wong)
Distribution: usa
Organization: University of California, Berkeley
Lines: 14