From: Christopher Faylor <cgf-use-the-mailinglist-please@sourceware.org>
To: dj@redhat.com, gdb-patches@sourceware.org,
Joel Brobecker <brobecker@adacore.com>,
gcc-patches@gcc.gnu.org, Eli Zaretskii <eliz@gnu.org>
Subject: Re: [RFA/libiberty] Enhance FILENAME_CMP for Windows filesystems
Date: Sat, 31 Mar 2007 22:40:00 -0000 [thread overview]
Message-ID: <20070331223959.GA23205@ednor.casa.cgf.cx> (raw)
In-Reply-To: <ubqi97hiq.fsf@gnu.org>
>On Wed, 28 Mar 2007 12:18:45 -0700, Joel Brobaker wrote:
>>This is a modest improvement, since there are many other things we
>>can do to enhance it (such as normalizing the path so that '//' and '/'
>>are treated as equal for instance). But this paves the path for
>>further improvements of that sort.
...
On Sat, Mar 31, 2007 at 02:57:01PM +0300, Eli Zaretskii wrote:
>While I realize that the original FILENAME_CMP macro did the same, as
>long as we are trying to do better, wouldn't it be nice if this
>function also collapsed multiple consecutive slashes or backslashes?
Joel already acknowledge that this was a possible future improvement.
If this is done, please be sure to preserve two slashes at the beginning
of a filename since Windows uses those.
cgf
next prev parent reply other threads:[~2007-03-31 22:40 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-28 19:17 Joel Brobecker
2007-03-28 19:31 ` DJ Delorie
2007-03-28 19:36 ` Joel Brobecker
2007-03-28 20:23 ` Joel Brobecker
2007-03-28 20:44 ` DJ Delorie
2007-03-29 20:56 ` Joel Brobecker
2007-03-29 21:02 ` Joel Brobecker
2007-03-29 21:03 ` Daniel Jacobowitz
2007-03-29 21:07 ` DJ Delorie
2007-03-29 21:44 ` Joel Brobecker
2007-03-31 11:57 ` Eli Zaretskii
2007-03-31 22:40 ` Christopher Faylor [this message]
2007-04-01 3:04 ` Eli Zaretskii
2007-04-02 7:01 ` Joel Brobecker
2007-04-01 20:58 ` Andreas Schwab
2007-04-02 6:34 ` Joel Brobecker
2007-04-02 11:21 ` Andreas Schwab
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=20070331223959.GA23205@ednor.casa.cgf.cx \
--to=cgf-use-the-mailinglist-please@sourceware.org \
--cc=brobecker@adacore.com \
--cc=dj@redhat.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