* John Cowan <co...@mercury.ccil.org> [111008 22:30]: > Here's my argument: file-exists? should return #t if the file definitely > exists and #f if it definitely doesn't, and should throw an exception > if the implementation cannot tell. In the case of ENAMETOOLONG, the > file *cannot* exist, so returning #f (and not throwing an exception) > is the Right Thing.
I see, thank you. This does sound reasonable for me. Felix, I bet you have fallen asleep by now :) What do you think? As to my dismay I have pushed the patch in the meantime but I would add the one line for the ENAMETOOLONG case as proposed by these gentlemen. Cheers, Christian -- Who can (make) the muddy water (clear)? Let it be still, and it will gradually become clear. Who can secure the condition of rest? Let movement go on, and the condition of rest will gradually arise. -- Lao Tse. _______________________________________________ Chicken-hackers mailing list Chicken-hackers@nongnu.org https://lists.nongnu.org/mailman/listinfo/chicken-hackers
