[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
PROBE-FILE
- To: greek@DEC-HUDSON.ARPA
- Subject: PROBE-FILE
- From: Rob MacLachlan <RAM@CMU-CS-C.ARPA>
- Date: Mon, 08 Apr 1985 19:33:00 -0000
- Cc: common-lisp@SU-AI.ARPA
- In-reply-to: Msg of 8 Apr 1985 15:02-EST from greek at DEC-HUDSON
The issue of how to get back more information about what is wrong
with a file was where we got bogged down before. I think that error
systems are the called for when you start to consider that sort of
issue. Any enumeration of all the things that can go wrong with
writing a file will also probably be hopelessly implementation
dependent. Unless you can come up with a simple, highly esthetic
proposal, I think we should stick with NIL for failure.
I suppose we could return an error-message string as a second
value, but anything along those lines seems like a sort of half-way
measure to me.
Rob