Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Joel Brobecker <brobecker@adacore.com>
To: gdb-patches@sourceware.org
Subject: Re: [RFC] Do not treat '\' as escape character on MinGW Windows  hosts
Date: Thu, 22 Apr 2010 10:37:00 -0000	[thread overview]
Message-ID: <20100422103718.GG19194@adacore.com> (raw)
In-Reply-To: <20100422023421.GA20111@ednor.casa.cgf.cx>

> I agree too except when we're talking about something that is
> essentially a UNIX tool.  And, I don't see how you can talk about the
> pain of doubling up the backslashes if you're talking about cutting and
> pasting.

Perhaps I shouldn't have based some of my argumentation on convenience,
since the degree of convenience varies from user to user [1], and thus
is a weak argument at best.

What we need to decide, as a group, is whether GDB is indeed a Unix tool,
and whether GDB should treat the Windows users as Unix users stuck on
Windows (I definitely feel that way everytime I have to do Windows work).
However, my observation of the group of users that sent me some feedback
do not have that perception at all. For them GDB is just a tool, not
a Unix tool, so they do not understand why GDB does not accept valid
Windows paths.

> I know I'll be outvoted here but I I hate cluttering code with MS-DOS
> workarounds.

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, we should support it
as a first class citizen.

-- 
Joel

[1]: Most of my Windows work is done remotely from a Linux machine,
     where copy/pasting is super easy (I have ctrl-y configured to paste
     in my xterm).


  parent reply	other threads:[~2010-04-22 10:37 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 [this message]
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
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=20100422103718.GG19194@adacore.com \
    --to=brobecker@adacore.com \
    --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