From ... Path: archiver1.google.com!news1.google.com!newsfeed.stanford.edu!canoe.uoregon.edu!logbridge.uoregon.edu!newsfeed1.bredband.com!bredband!uio.no!nntp.uio.no!ifi.uio.no!not-for-mail From: Erik Naggum Newsgroups: comp.lang.lisp Subject: Re: Checking for EOF Date: 14 Nov 2002 00:37:06 +0000 Organization: Naggum Software, Oslo, Norway Lines: 25 Message-ID: <3246223026951655@naggum.no> References: <4lm4057dr.fsf@beta.franz.com> <47kfj6be0.fsf@beta.franz.com> <3246042568510031@naggum.no> <4u1in4sot.fsf@beta.franz.com> <3246137832742017@naggum.no> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: maud.ifi.uio.no 1037234227 20355 129.240.65.205 (14 Nov 2002 00:37:07 GMT) X-Complaints-To: abuse@ifi.uio.no NNTP-Posting-Date: 14 Nov 2002 00:37:07 GMT Mail-Copies-To: never User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.2 Xref: archiver1.google.com comp.lang.lisp:46543 * Kaz Kylheku | C-d causes the read() system call to return immediately. Thank you for re-explaining what was obviously impossible to understand from what I already posted. | Line-oriented mode *is* device-level reads, and there really is no | true end-of-file. Please work harder to get the point. | So to the applications, it looks like there really is a piece of hardware | that delivers entire lines of input to the operating system. Wrong. | Sorry about the long off topic rant about arcane obscurities. ;) It would have been OK if you got it right. -- Erik Naggum, Oslo, Norway Act from reason, and failure makes you rethink and study harder. Act from faith, and failure makes you blame someone and push harder.