From: Joel Brobecker <brobecker@adacore.com>
To: Chris Moller <cmoller@redhat.com>, gcc-patches@gcc.gnu.org
Cc: gdb-patches@sourceware.org
Subject: Re: [RFC] Do not treat '\' as escape character on MinGW Windows hosts
Date: Thu, 22 Apr 2010 12:33:00 -0000 [thread overview]
Message-ID: <20100422123308.GA12680@adacore.com> (raw)
In-Reply-To: <4BD03906.5090109@redhat.com>
> >Understood, and it's not obvious to me that you'll be outvoted. This
> >is why I am asking for comments more than a review at this point.
> >I would like to challenge the "workaround" term, though :-P. I much as
> >I dislike Windows (and believe me, I really dislike this platform),
> >I think that if we are going to support Windows,
>
> That, then, is the fundamental question. Certainly, Windows support
> adds to code complexity, which is always a bad thing.
Let's imagine that we have a bug in the software, can we reasonably tell
the user that his bug will not be fixed because the fix complexifies
the code? To a Windows user, not being able to use backslashes in paths
is a bug!
--
Joel
next prev parent reply other threads:[~2010-04-22 12:33 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-21 20:34 Joel Brobecker
2010-04-21 22:08 ` Christopher Faylor
2010-04-22 0:17 ` Joel Brobecker
2010-04-22 2:34 ` Christopher Faylor
2010-04-22 8:17 ` Mark Kettenis
2010-04-22 10:37 ` Joel Brobecker
2010-04-22 11:51 ` Joel Brobecker
2010-04-22 12:01 ` Pierre Muller
2010-04-22 12:26 ` Joel Brobecker
2010-04-22 11:54 ` Chris Moller
2010-04-22 12:33 ` Joel Brobecker [this message]
2010-04-22 11:49 ` Chris Moller
2010-04-22 12:47 ` André Pönitz
2010-05-05 18:49 ` Joel Brobecker
2010-05-06 23:56 ` Sergio Durigan Junior
2010-06-04 21:53 ` Tom Tromey
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=20100422123308.GA12680@adacore.com \
--to=brobecker@adacore.com \
--cc=cmoller@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=gdb-patches@sourceware.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