From mboxrd@z Thu Jan  1 00:00:00 1970
From: "Eli Zaretskii" <eliz@is.elta.co.il>
To: orjan.friberg@axis.com
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFC]: Solib search (Was: Re: Cross solib support; continued)
Date: Tue, 27 Nov 2001 12:42:00 -0000
Message-ID: <9743-Tue27Nov2001224135+0200-eliz@is.elta.co.il>
References: <3BEAA3A0.586B3046@axis.com> <20011108110955.A12240@nevyn.them.org> <3C03AB51.DB27B3D4@axis.com> <3405-Tue27Nov2001175932+0200-eliz@is.elta.co.il> <3C03D84E.26E8B4F9@axis.com>
X-SW-Source: 2001-11/msg00507.html
Message-ID: <20011127124200.SvFr0e6em0mgBFJlXOnCGozG-cQj7L8lALRrNhJgLdc@z>

> Date: Tue, 27 Nov 2001 19:15:42 +0100
> From: Orjan Friberg <orjan.friberg@axis.com>
> 
> Eli Zaretskii wrote:
> > 
> > This is not how one should test for an absoulte file name portably,
> > and incrementing in_pathname by one is not how you portably make it a
> > relative file name.
> 
> Yes, I know (from my original post):
> 
> > (It won't work with DOS based file
> > systems, as the dir separator could be '\\', but that would be easy to add.)

I've seen that, but you only mentioned the backslash nuisance.  My
point was that there are more subtle problems: the first character of
an absolute file name doesn't have to be a slash or a backslash.

> Thanks for the suggestion on how to do it correctly though; I'll
> incorporate it.

You are welcome.