Path: utzoo!news-server.csri.toronto.edu!rutgers!sun-barr!cs.utexas.edu!hellgate.utah.edu!caen!zaphod.mps.ohio-state.edu!wuarchive!udel!rochester!miller
From: miller@cs.rochester.edu (Brad Miller)
Newsgroups: comp.lang.lisp
Subject: conditions
Message-ID: <1991Mar13.180714.12683@cs.rochester.edu>
Date: 13 Mar 91 18:07:14 GMT
Reply-To: miller@cs.rochester.edu
Organization: University of Rochester Computer Science Department
Lines: 17

Is there a normal way to signal a parse-error? Cltl 2/e doesn't define a
subtype of error that looks obvious; what I'm looking for is something akin
to symbolics sys:read-error, that is, an error you get at read-time which
if you are typing to the top level, just lets you rubout and retype rather than
dumping you into the debugger.

program-error seems too strong. 

If "the right way to do it" involves writing something myself, I'd like a hint;
I'm new to conditions, and it isn't immediately obvious to me how I can get the
effect of default-global-handlers on the symbolics.

Regards,
-- 
----
Brad Miller             U. Rochester Comp Sci Dept.
miller@cs.rochester.edu {...allegra!rochester!miller}