From: Kamil Iskra <kamil@dwd.interkom.pl>
To: Jeffrey A Law <law@hurl.cygnus.com>
Cc: egcs@cygnus.com
Subject: Re: Predefining __OS_DOS__
Date: Sat, 12 Dec 1998 14:36:00 -0000 [thread overview]
Message-ID: <Pine.LNX.3.96.981212145654.713G-100000@jinks.home> (raw)
In-Reply-To: <12435.913395755@hurl.cygnus.com>
On Fri, 11 Dec 1998, Jeffrey A Law wrote:
> > What would be most helpful for those of us using non-Unix systems
> > (whether Win32, OS/2, DOS, VMS or other) is not to embed knowledge
> > about things like filenames all over the place, but instead use functions
> > or macros like IS_DIR_SEP(X), IS_ROOTED_PATH(X) to test for directory
> > separators or rooted paths.
[snip]
> Yes. DIR_SEPARATOR shows up in cpp and other parts of gcc, but it's not
> used as often as it should be. Using it more would allow for some cleanups
> of both the dos and vms support.
Using DIR_SEPARATOR is *NOT* appropriate, strictly speaking. It implies
that only one character can be used for dir separation. This is true under
UNIX, but not under AmigaOS, for example, where ':' can be used in some
cases (and, unlike under Dos, it is usually NOT followed by
DIR_SEPARATOR).
/ Kamil Iskra AmigaOS Linux/i386 Linux/m68k \
| GeekGadgets m68k-amigaos GCC maintainer |
| iskra@student.uci.agh.edu.pl kiskra@ernie.icslab.agh.edu.pl |
\ kamil@dwd.interkom.pl http://student.uci.agh.edu.pl/~iskra /
next prev parent reply other threads:[~1998-12-12 14:36 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-12-11 2:40 Geert Bosch
1998-12-11 9:04 ` Jeffrey A Law
1998-12-12 14:36 ` Kamil Iskra [this message]
[not found] ` <12435.913395755.cygnus.egcs@hurl.cygnus.com>
1998-12-11 10:07 ` Tom Tromey
1998-12-11 13:49 ` Jeffrey A Law
-- strict thread matches above, loose matches on Subject: below --
1998-12-12 15:36 Geert Bosch
1998-12-07 16:15 Mike Stump
1998-12-05 4:00 Peter Gerwinski
1998-12-06 2:57 ` Jeffrey A Law
1998-12-06 7:05 ` Peter Gerwinski
1998-12-07 22:56 ` Jeffrey A Law
1998-12-10 16:45 ` Peter Gerwinski
1998-12-10 23:53 ` Jeffrey A Law
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=Pine.LNX.3.96.981212145654.713G-100000@jinks.home \
--to=kamil@dwd.interkom.pl \
--cc=egcs@cygnus.com \
--cc=law@hurl.cygnus.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).