Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Joel Brobecker <brobecker@adacore.com>
Cc: danny.backx@scarlet.be, drow@false.org, gdb-patches@sourceware.org
Subject: Re: shared lib dos filename style - one more question
Date: Tue, 13 Oct 2009 18:12:00 -0000	[thread overview]
Message-ID: <83my3vi2lg.fsf@gnu.org> (raw)
In-Reply-To: <20091013052437.GJ5272@adacore.com>

> Date: Mon, 12 Oct 2009 22:24:37 -0700
> From: Joel Brobecker <brobecker@adacore.com>
> Cc: danny.backx@scarlet.be, drow@false.org, gdb-patches@sourceware.org
> 
> > > What should unixify() do ?
> > > 1.  /path/to/a -> /path/to/a
> > > 2.  \path/to/a -> /path/to/a
> > > 3.  \path\to\a -> /path/to/a
> > > 4.  c: -> .
> > > 5.  c:\path\to\a -> /path/to/a
> > 
> > If unixify is supposed to support Windows file semantics, then the
> > last 2 cases are incorrect, IMO.  4 should return "c:." and 5
> > "c:/path/to/a".
> 
> Actually, I think in this case "unixify" would mean trying to make
> sense out of Windows path on a Unix machine: The target sent us
> c:\path\to\dll, and we're trying to find that dll on the host.

What is the use-case in which this can happen?


  parent reply	other threads:[~2009-10-13 18:12 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-26 13:49 Danny Backx
2009-10-07 20:05 ` Danny Backx
2009-10-07 20:11   ` Daniel Jacobowitz
2009-10-08 16:01     ` Danny Backx
2009-10-09 17:36       ` Joel Brobecker
2009-10-09 18:58         ` Danny Backx
2009-10-10  2:19           ` Joel Brobecker
2009-10-12 20:05             ` Danny Backx
2009-10-12 20:28               ` Eli Zaretskii
2009-10-13  5:24                 ` Joel Brobecker
2009-10-13 10:57                   ` Pedro Alves
2009-10-13 15:30                     ` Joel Brobecker
2009-10-13 18:23                       ` Eli Zaretskii
2009-10-13 18:12                   ` Eli Zaretskii [this message]
2009-10-13 18:19                     ` Daniel Jacobowitz
2009-10-12 20:45             ` Daniel Jacobowitz
2009-10-13  5:21               ` Joel Brobecker
2009-10-13 15:51                 ` Daniel Jacobowitz
2009-10-14 20:18               ` Danny Backx
2009-10-17  4:16                 ` Joel Brobecker

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=83my3vi2lg.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=brobecker@adacore.com \
    --cc=danny.backx@scarlet.be \
    --cc=drow@false.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