[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
READing HUNKs
- To: (BUG LISP) at MIT-MC
- Subject: READing HUNKs
- From: ALAN at MIT-MC (Alan Bawden)
- Date: Sat, 22 Mar 80 02:20:00 GMT
- Original-date: 21 MAR 1980 2120-EST
Well If we are going to try and have READ grok hunks then the
following should be fixed:
(cons (hunk 1 2 3) (hunk 1 2 3))
((1 . 2 . 3 .) 1 . 2 . 3 .) ;Hmmm... the printer seems to have made
;an interesting optimization!
'((1 . 2 . 3 .) 1 . 2 . 3 .) ;Let's see if the reader can hack it...
((1 . 2 . 3 .) . 1 . 2 . 3 .) ;Doesn't look good...
(typep *)
HUNK4 ;Nope
Sigh.
While I have you all listening let me plead once again for a hook in
the printer to allow me to redefine the way hunks print. Since many
people have built structure packages on top of hunks, it doesn't seem
too unreasonable to provide a simple way to change the way they print.
I know there is such a hook now that is specific to a certain use. I
would hope that the people using this hook would be willing and able
to build their hacks on top of some more general hook that the rest of
us could use for our own purposes. Please?