Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Andreas Schwab <schwab@linux-m68k.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Jonathan Larmour <jifl@eCosCentric.com>,
	 pedro@codesourcery.com,  gdb-patches@sourceware.org
Subject: Re: Fix doc index name on Windows
Date: Sat, 27 Nov 2010 09:24:00 -0000	[thread overview]
Message-ID: <m2wrnzp1ab.fsf@whitebox.home> (raw)
In-Reply-To: <837hg06oup.fsf@gnu.org> (Eli Zaretskii's message of "Fri, 26 Nov	2010 18:17:50 +0200")

Eli Zaretskii <eliz@gnu.org> writes:

> I didn't mean in the manual, I meant in the code.  Most packages
> assume that any file name is valid, and that file names are just
> case-sensitive strings.  Some packages (GDB is one) are nice enough to
> admit that file-name comparison should be case-insensitive on
> non-Posix platforms.  But I can count on fingers of one hand those
> that have code fragments that cater to more serious limitations or
> idiosyncrasies of non-Posix platforms.

You can count on the fingers of one hand those packages that actually
have to care about conflicting file names in the first place.  Most
programs either don't write files, or they use the file names supplied
by the user.  Generating file names from user input is rather uncommon.

Andreas.

-- 
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."


  reply	other threads:[~2010-11-27  9:24 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-25 17:40 Jonathan Larmour
2010-11-25 18:21 ` Eli Zaretskii
2010-11-25 18:47   ` Jonathan Larmour
2010-11-26 11:55     ` Eli Zaretskii
2010-11-26 12:03       ` Pedro Alves
2010-11-26 12:52         ` Eli Zaretskii
2010-11-26 13:05           ` Pedro Alves
2010-11-26 15:07           ` Jonathan Larmour
2010-11-26 16:15             ` Eli Zaretskii
2010-11-27  9:24               ` Andreas Schwab [this message]
2010-11-26 15:12       ` Jonathan Larmour
2010-11-26 16:08         ` Eli Zaretskii

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=m2wrnzp1ab.fsf@whitebox.home \
    --to=schwab@linux-m68k.org \
    --cc=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    --cc=jifl@eCosCentric.com \
    --cc=pedro@codesourcery.com \
    /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