From: Ian Lance Taylor <ian@zembu.com>
To: eliz@gnu.org
Cc: binutils@sourceware.cygnus.com
Subject: Re: DOS/Windows-related changes in the include subdirectory
Date: Mon, 06 Sep 1999 08:10:00 -0000 [thread overview]
Message-ID: <19990906150939.10027.qmail@daffy.airs.com> (raw)
In-Reply-To: <199909060814.EAA23317@mescaline.gnu.org>
Date: Mon, 6 Sep 1999 04:14:19 -0400
From: Eli Zaretskii <eliz@gnu.org>
This adds a new file with several macros for platform-independent
handling of file names.
1999-07-08 Eli Zaretskii <eliz@is.elta.co.il>
* filenames.h: New file.
(DOSISH_FILENAMES, MONOCASE_FILENAMES, FILENAME_CMP): New macros.
It might be nice to use the same set of macros that gcc uses, rather
than invent our own. In gcc.c I see things like PATH_SEPARATOR,
DIR_SEPARATOR, DIR_SEPARATOR_2, IS_DIR_SEPARATOR,
HAVE_DOS_BASED_FILESYSTEM.
Ian
next prev parent reply other threads:[~1999-09-06 8:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-09-06 1:14 Eli Zaretskii
1999-09-06 8:10 ` Ian Lance Taylor [this message]
1999-09-06 10:22 ` Eli Zaretskii
1999-09-06 10:31 ` Ian Lance Taylor
1999-09-06 11:20 ` Mark E.
1999-09-07 5:54 ` Eli Zaretskii
1999-09-07 5:49 ` 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=19990906150939.10027.qmail@daffy.airs.com \
--to=ian@zembu.com \
--cc=binutils@sourceware.cygnus.com \
--cc=eliz@gnu.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).