Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Joel Brobecker <brobecker@adacore.com>
To: Danny Backx <danny.backx@scarlet.be>
Cc: gdb-patches <gdb-patches@sourceware.org>,
	Eli Zaretskii <eliz@gnu.org>,
		Pedro Alves <pedro@codesourcery.com>,
		Daniel Jacobowitz <drow@false.org>
Subject: Re: shared lib dos filename style - one more question
Date: Sat, 17 Oct 2009 04:16:00 -0000	[thread overview]
Message-ID: <20091017041543.GJ5272@adacore.com> (raw)
In-Reply-To: <1255551583.10921.271.camel@pavilion>

> Ok so I guess the table becomes :
> 
> > 1.  /path/to/a -> /path/to/a
> > 2.  \path/to/a -> /path/to/a
> > 3.  \path\to\a -> /path/to/a
> > 4.  c: -> c:
> > 5.  c:\path\to\a -> c:/path/to/a
> 
> so the only thing that happens is backslash to forward slash
> translation.

That is also my understanding from the previous discussions,
except also for the case insensitivity.

> Do you mean that the call to unixify() should happen in openp() instead
> of in solib_find() ? There's also a call to open() so I guess this
> should be changed as well.

It's a little foggy in my memory, right now, and I don't have much
time to dig further.  But you have to be a little careful - I don't
think a call to open can be replaced by a call to openp. But what
Daniel probably meant was that we shouldn't limit this solution to
just solib_find.  So yes, probably something in in openp. Or perhaps
a new routine that does DOS-style file matching on Unix hosts that
openp and solib_find could call.

-- 
Joel


      reply	other threads:[~2009-10-17  4:16 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
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 [this message]

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=20091017041543.GJ5272@adacore.com \
    --to=brobecker@adacore.com \
    --cc=danny.backx@scarlet.be \
    --cc=drow@false.org \
    --cc=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    --cc=pedro@codesourcery.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