0.8.2.53:
Fixed hanging-on-reader-error in Darwin (and Solaris, it turns
out):
... Here's the deal: lseek(), on "certain devices", has
"unspecified consequences"
... said devices include, empirically, /dev/stdin
... so lseek was merrily returning a success code despite
clearly being incapable of rewinding the input stream
... so in our new error-reporting for reader errors, we were
assuming because of the success value that we could
read the erroneous input into a buffer...
... whereas we were rather sitting there waiting for more input.
... So protect the rereading code with an INTERACTIVE-STREAM-P.