From: David Brown <git@davidb.org>
To: Andreas Ericsson <ae@op5.se>
Cc: skimo@liacs.nl, Rob McDonald <robm@asdl.gatech.edu>, git@vger.kernel.org
Subject: Re: Possibility of a MinGW version?
Date: Sat, 24 Dec 2005 08:40:12 -0800 [thread overview]
Message-ID: <20051224164011.GA6737@old.davidb.org> (raw)
In-Reply-To: <43AD21D7.5060306@op5.se>
On Sat, Dec 24, 2005 at 11:24:23AM +0100, Andreas Ericsson wrote:
> Sven Verdoolaege wrote:
> >On Sat, Dec 24, 2005 at 11:09:39AM +0100, Andreas Ericsson wrote:
> >
> >>The worst trouble you're likely to run into is all the hardcoded paths.
> >>They are everywhere and ofcourse use the / for path entity separation.
> >
> >
> >AFAIR, '/' is a valid path separator on Windows.
> >It's just command.com (does that still exist?) that insisted on '\\'
> >separators.
>
> Are you sure? I've seen lots of porting patches that transliterate those
> to '\\'. Perhaps those who wrote those patches just took for granted
> that it was needed, the same as I did.
AFAIK all of the Win32 APIs accept either forward or backward slash as a
separator. It has been this way since when they added directories to DOS.
What doesn't always accept forward slashes are commandline utilities that
are using '/' as an option separator. Most of them these days will accept
the '/', at least in many circumstances.
Dave
next prev parent reply other threads:[~2005-12-24 16:40 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-24 2:34 Possibility of a MinGW version? Rob McDonald
2005-12-24 10:09 ` Andreas Ericsson
2005-12-24 10:18 ` Sven Verdoolaege
2005-12-24 10:24 ` Andreas Ericsson
2005-12-24 12:07 ` Johannes Schindelin
2005-12-24 16:40 ` David Brown [this message]
2005-12-24 13:51 ` Rob McDonald
2005-12-24 14:16 ` Johannes Schindelin
2005-12-25 17:16 ` Rob McDonald
2005-12-31 16:39 ` Christopher Faylor
2005-12-31 21:53 ` H. Peter Anvin
2006-01-01 5:25 ` Christopher Faylor
2005-12-31 16:40 ` Christopher Faylor
2005-12-24 17:58 ` Junio C Hamano
2005-12-24 23:44 ` Andreas Ericsson
2005-12-25 1:47 ` Junio C Hamano
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=20051224164011.GA6737@old.davidb.org \
--to=git@davidb.org \
--cc=ae@op5.se \
--cc=git@vger.kernel.org \
--cc=robm@asdl.gatech.edu \
--cc=skimo@liacs.nl \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.