-
There are three reasons for remembering that EOF has happened on an input stream:
1) For regular files and block devices: The normal situation
is that a file's size does not change while it is being read
by an application. This is the only supported situation.
The mere fact that stat() returns an st_size information
indicates that files are supposed to stay at the same size...
2009-11-24 01:37:25 UTC by haible
-
sds committed patchset 14522 of module clisp to the CLISP - an ANSI Common Lisp CVS repository, changing 1 files.
2009-11-23 21:32:40 UTC by sds
-
just to clarify, this behavior can cause problems with special files ("COM1" on woe32 and "/proc/*" on unix).
.
2009-11-23 20:44:31 UTC by sds
-
when clisp reaches eof, it remembers it and never clears the condition even if when the file on disk changes.
sbcl and C (both FILE/fopen and int/fd/open interfaces) do not exhibit this behavior.
2009-11-23 20:35:19 UTC by sds
-
sds committed patchset 14521 of module clisp to the CLISP - an ANSI Common Lisp CVS repository, changing 1 files.
2009-11-23 17:31:19 UTC by sds
-
vtz committed patchset 14520 of module clisp to the CLISP - an ANSI Common Lisp CVS repository, changing 5 files.
2009-11-21 20:54:58 UTC by vtz
-
sds committed patchset 14519 of module clisp to the CLISP - an ANSI Common Lisp CVS repository, changing 1 files.
2009-11-20 14:50:39 UTC by sds
-
sds committed patchset 14518 of module clisp to the CLISP - an ANSI Common Lisp CVS repository, changing 2 files.
2009-11-19 21:18:36 UTC by sds
-
sds committed patchset 14517 of module clisp to the CLISP - an ANSI Common Lisp CVS repository, changing 2 files.
2009-11-19 21:16:20 UTC by sds
-
sds committed patchset 14516 of module clisp to the CLISP - an ANSI Common Lisp CVS repository, changing 12 files.
2009-11-19 21:02:22 UTC by sds
