From: Julian S. <der...@we...> - 2008-07-01 01:34:29
|
"Nathan Froyd" <fr...@gm...> writes: > On Mon, Jun 30, 2008 at 7:58 PM, Julian Stecklina <der...@we...> wrote: >> FYI, I opened a Linux kernel bug and it was almost instantly rejected: >> >> http://bugzilla.kernel.org/show_bug.cgi?id=11014#c2 >> >> Regarding the comment "It is weird that lisp has such a strange file io >> implementation.": Is there any rationale for doing file I/O this way? > > I'd be curious as to what other way one would do file I/O if you want > to support doing I/O on multiple sockets and files simultaneously. I > mean, this has worked for *years*. (And no, whiz-bangy Linux-specific > stuff doesn't count at the moment, at least not until something like > iolib lands in SBCL.) Btw, I just tried CMUCL 19c suspecting that it would exhibit the same behaviour, but it seems fine with sysfs files: * (with-open-file (in "/sys/class/power_supply/AC/type") (read-line in)) "Mains" NIL Does anyone have a clue what they do differently? Regards, -- Julian Stecklina Well, take it from an old hand: the only reason it would be easier to program in C is that you can't easily express complex problems in C, so you don't. - Erik Naggum (in comp.lang.lisp) (Spam-Experiment: http://cthulhu.c3d2.de/~astro/badpit.html ) |