[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Why does @INFORMATION (ABOUT) FILES ... say "restricted JFN"?
- To: Jon L White <JONL at MIT-MC>
- Subject: Why does @INFORMATION (ABOUT) FILES ... say "restricted JFN"?
- From: FEINBERG at CMU-20C
- Date: Wed, 3 Mar 82 02:59:00 GMT
- Cc: BUG-MACLISP at MIT-MC
- Original-date: 2 March 1982 21:59-EST (Tuesday)
I beg to differ with you, JONL. Here is a excerpt from
;HERE TO ALLOCATE A FRESH JFN AND OPEN THE FILE
OPEN3D: PUSH FXP,TT ;SAVE THE TTSAR
PUSH FXP,(T) ;COPY THE GIVEN DEVICE NAMES ONTO THE STACK
PUSHJ P,6BTTLS ;CONVERT TO A NAMESTRING IN PNBUF
POP FXP,TT ;GET TTSAR
MOVE T,(FXP) ;RESTORE MODE BITS IN T
MOVSI 1,(GJ%ACC+GJ%SHT) .SEE .GJDEF
TLOA 1,(GJ%OLD) ;FOR INPUT OR APPEND, WE WANT AN EXISTING FILE
TLO 1,(GJ%FOU+GJ%NEW) ;FOR OUTPUT, A NON-EXISTENT FILE
GTJFN ;GET A JFN
The line MOVSI 1,(GJ%ACC+GJ%SHT) sets the Restricted Access bit.
There are apparently many GJ%ACCs throughout QIO.MID. If there is a
good reason for them to be there, that is one thing. Denying that
they are there is a different story. I would proposed eliminating
GJ%ACC from all GTJFN calls. This would make debugging easier.