[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]


1)  When i said 'image [binary]' i meant 36. bit bytes only;  ITS
conveniently calls that 'image', and lisp knowingly uses 'image' as a
tag for something else.
2)  What i was suggesting was a disjunction of the sizes of bytes that
lisp uses for inputting/outputting and user-accessing.  EG, lisp
could read off a device in 36. bit bytes, but give it to the user
in 7. bit bytes (and hack filepos accordingly).
The lisp internals look like they could hack this without too much
trouble;  in fact, they look like they could hack arbitrary byte sizes
now, if open would only take that option.