[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Overly terse error messages.
- To: bug-lisp @ mit-ai
- Subject: Overly terse error messages.
- From: Scott Fahlman at CMU-10A (C380SF50)
- Date: Wed, 31 Jan 79 05:32:00 GMT
- Cc: forgy at CMU-10A
- Original-date: 31 Jan 1979 0032-EST
Why doesn't the default error handler for GC overflow print out the name
of the offending space? It appears that there is no way to retrieve this name
once the break has been taken -- or am I missing something? I know that
a user can define his own handler to do this, but I feel that the default could
be more informative. The screwee in this case is Lanny Forgy.