[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
this doesn't have much to do with any new monitor, I suspect
- To: bug-lisp at mc
- Subject: this doesn't have much to do with any new monitor, I suspect
- From: Chris Ryland <CPR at MIT-EECS>
- Date: Tue, 13 Jan 81 18:22:00 GMT
- Cc: Keshav at MIT-XX
- Original-date: Tuesday, 13 January 1981 13:22-EST
Date: Mon, 12 Jan 81 22:03:00 GMT
Original-Date: Monday, 12 January 1981 17:03-EST
From: KESHAV at MIT-XX
To: cpr at MIT-XX
Re: A Bug
The function writeablep in Maclisp is defined in the fasl file <maclisp>purep.
fasl. My guess is that it checks for write protection violations. Until
yesterday, calling this function with an output file (in Maclisp) gave t(rue).
It still does so in Maclisp on ML. However, your new monitor gives a
write protection error.
One LISP program that shows this is -
(load '((dsk maclisp) purep fasl))
(setq outfilep (open '(my output) 'out))
This should return t.