[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: More (unrelated) EVALHOOK issues
- To: Kent M Pitman <KMP@MIT-MC.ARPA>
- Subject: Re: More (unrelated) EVALHOOK issues
- From: Dave Dyer <DDYER@USC-ISIB.ARPA>
- Date: Fri, 07 Sep 1984 02:56:00 -0000
- Cc: common-lisp@SU-AI.ARPA
- In-reply-to: (Message from "Kent M Pitman <KMP@MIT-MC.ARPA>" of 6 September 1984 18:16-EDT)
I agree that this is a lack in EVALHOOK, but the same also occurs
in debugging generally. The problem is that not enough state of
the interpreter is available to analysis/error handling tools, of
which an EVALHOOK routine is a good example.
In Interlisp, this isn't a problem because the temporaries of the
interpreter are explicitly available.