From: "Dave Korn" <dave.korn@artimi.com>
To: "'Eli Zaretskii'" <eliz@gnu.org>,
"'Joel Brobecker'" <brobecker@adacore.com>
Cc: <gcc-patches@gcc.gnu.org>, <gdb-patches@sourceware.org>
Subject: RE: [RFA/libiberty] Fix documentation issues in filename_cmp.c
Date: Fri, 06 Apr 2007 10:00:00 -0000 [thread overview]
Message-ID: <036d01c77832$60baeef0$2e08a8c0@CAM.ARTIMI.COM> (raw)
In-Reply-To: <u3b3d50ul.fsf@gnu.org>
On 06 April 2007 10:06, Eli Zaretskii wrote:
>> 1. Fold multiple consecutive slash/backslash characters into single
>> slash/backslash;
> (However, note that, as Chris pointed out, double slash at the
> beginning of a file name, as in "//foo/bar", are significant on
> Windows.)
JFTR, it's a POSIX requirement too:
http://www.opengroup.org/onlinepubs/009695399/basedefs/xbd_chap04.html#tag_04_
11
" A pathname that begins with two successive slashes may be interpreted in an
implementation-defined manner, although more than two leading slashes shall be
treated as a single slash. "
cheers,
DaveK
--
Can't think of a witty .sigline today....
next prev parent reply other threads:[~2007-04-06 10:00 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-05 17:27 Joel Brobecker
2007-04-05 18:36 ` DJ Delorie
2007-04-06 6:02 ` Joel Brobecker
2007-04-05 18:44 ` Eli Zaretskii
2007-04-06 6:10 ` Joel Brobecker
2007-04-06 9:05 ` Eli Zaretskii
2007-04-06 10:00 ` Dave Korn [this message]
2007-04-07 17:35 ` Daniel Jacobowitz
2007-04-07 17:52 ` Eli Zaretskii
2007-04-11 7:24 ` Joel Brobecker
2007-04-11 18:28 ` Eli Zaretskii
2007-04-11 20:33 ` Ian Lance Taylor
2007-05-03 15:36 ` [RFA/libiberty] use TOLOWER instead of tolower " Joel Brobecker
2007-05-03 16:31 ` Ian Lance Taylor
2007-05-03 23:40 ` Joel Brobecker
2007-05-04 7:18 ` Eli Zaretskii
2007-04-11 7:27 ` [RFA/libiberty] Fix documentation issues " Joel Brobecker
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='036d01c77832$60baeef0$2e08a8c0@CAM.ARTIMI.COM' \
--to=dave.korn@artimi.com \
--cc=brobecker@adacore.com \
--cc=eliz@gnu.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=gdb-patches@sourceware.org \
/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