[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
GC-OVERFLOW, GC-LOSSAGE
- To: GSB at MIT-MC
- Subject: GC-OVERFLOW, GC-LOSSAGE
- From: JONL at MIT-MC (Jon L White)
- Date: Wed, 1 Nov 78 17:00:00 GMT
- Cc: (BUG LISP) at MIT-MC
- Original-date: 1 NOV 1978 1200-EST
GC-OVERFLOW isn't really supposed to be an error, which is why there is
no errframe. GC-LOSSAGE is supposed to be an error, with an errframe,
but sometimes facilities are so cramped that the only thing possible
is to print out a message and punt back to toplevel. What kind of
message was being printed out by GC-OVERFLOW that made you think it
was a standard error message?