From: Eli Zaretskii <eliz@gnu.org>
To: Jonathan Larmour <jifl@eCosCentric.com>
Cc: pedro@codesourcery.com, gdb-patches@sourceware.org
Subject: Re: Fix doc index name on Windows
Date: Fri, 26 Nov 2010 16:15:00 -0000 [thread overview]
Message-ID: <837hg06oup.fsf@gnu.org> (raw)
In-Reply-To: <4CEFCD32.40203@eCosCentric.com>
> Date: Fri, 26 Nov 2010 15:07:30 +0000
> From: Jonathan Larmour <jifl@eCosCentric.com>
> CC: Pedro Alves <pedro@codesourcery.com>, gdb-patches@sourceware.org
>
> > IMO, "broken" is an exaggeration. How many tools did you see that
> > care about having their files produced on Unix be compatible with
> > NTFS? How many maintainers of GNU packages do you know who would even
> > consider a possibility of inserting NTFS-related limitations into
> > their codebase?
>
> Evidently quite a few because my patch just brings GDB into line with what
> GAS, binutils, BFD, CPP, and LD's docs explicitly do. In this respect GDB
> is the odd one out.
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.
> People don't use a special cross version of makeinfo. GDB doesn't try and
> invoke one, for example. Which is quite right.
Well, evidently it is NOT right, because stock makeinfo doesn't care
about this issue, except if you actually run it on Windows.
If we are going to have a coding convention that the Index nodes
should not be called just "Index", this should be at least in the
Texinfo manual, if not in standards.texi.
next prev parent reply other threads:[~2010-11-26 16:15 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 [this message]
2010-11-27 9:24 ` Andreas Schwab
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=837hg06oup.fsf@gnu.org \
--to=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