From: John Carr <jfc@MIT.EDU>
To: caml-list@inria.fr
Subject: Re: [Caml-list] Unix.stat sometimes fails on Win32 port
Date: Wed, 06 Aug 2003 13:01:51 -0400 [thread overview]
Message-ID: <200308061701.NAA19471@no-knife.mit.edu> (raw)
In-Reply-To: Your message of "Wed, 06 Aug 2003 09:21:43 PDT." <20030806162143.GA29738@davidb.org>
> But, it would be just as valid to argue that Unix has a bug in that it
> doesn't detect an incorrectly formed pathname.
It's not a bug, it's a feature.
POSIX requires that operations on "/directory/" and "/directory"
behave identically in most situations. Since the module is named
"Unix" it ought to follow the Unix convention.
-------------------
To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr
Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/
Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
prev parent reply other threads:[~2003-08-06 17:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-06 10:02 Richard Jones
2003-08-06 14:39 ` David Brown
2003-08-06 14:49 ` Richard Jones
2003-08-06 16:21 ` David Brown
2003-08-06 17:01 ` John Carr [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200308061701.NAA19471@no-knife.mit.edu \
--to=jfc@mit.edu \
--cc=caml-list@inria.fr \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).