CMUCL only understands Unix end-of-line conventions. So, read-line won't properly deal with files whose lines in in crlf.
Tim On Saturday, November 2, 2002, at 08:36 PM, Will wrote: > Hello, > > I've run across a problem with read-line, and I can't seem to get it to > work as expected (as it works in CLISP). > > I have attached the text file that I am using. > > The following code seems to give me an improperly terminated string. > > (setf foo > (with-open-file (str > (make-pathname :name "test") > :direction :input) > (read-line str nil "eof"))) > > When I run the above code, the output is > "Features > I would expect > "Features" > > > The following code, then gives me: > (format t "~Aabc" foo) > abctures > NIL > I would expect > Features > NIL > > In case the text file is marred in the transfer, it includes the text > Features<crlf> > where <crlf> refers to the corresponding ASCII codes. > > I am running: > CMU Common Lisp 18d+, built 2002-09-13 on melbourne, running on > hscslack > Send questions to [EMAIL PROTECTED] and bug reports to > [EMAIL PROTECTED] > Loaded subsystems: > Python 1.0, target Intel x86 > CLOS based on PCL version: September 16 92 PCL (f) > > *features* > > (:PCL-STRUCTURES :PORTABLE-COMMONLOOPS :PYTHON :PCL :LINKAGE-TABLE > :GLIBC2 > :LINUX :UNIX :GENCGC :MP :I486 :X86 :IEEE-FLOATING-POINT :ANSI-CL > :COMMON-LISP > :COMMON :NEW-COMPILER :HASH-NEW :CONSERVATIVE-FLOAT-TYPE > :RANDOM-MT19937 > :RELATIVE-PACKAGE-NAMES :CMU18D :CMU18 :CMU) > > > Cheers~ > > Will > > -- > To cast off the idiot Questioner who is always questioning, > But never capable of answering; who sits with a sly grin > Silent plotting when to question, like a thief in a cave; > Who publishes doubt & calls it knowledge; whose Science is > Despair > --William Blake > > > -- Attached file included as plaintext by Listar -- > -- File: test > > Features > >
