Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Stan Shebs <stanshebs@earthlink.net>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Daniel Jacobowitz <drow@false.org>,
	vladimir@codesourcery.com,   gdb-patches@sources.redhat.com
Subject: Re: Better realpath
Date: Wed, 18 Jun 2008 18:39:00 -0000	[thread overview]
Message-ID: <4859280A.8000006@earthlink.net> (raw)
In-Reply-To: <uabhmlgvu.fsf@gnu.org>

Eli Zaretskii wrote:
>> Date: Sat, 14 Jun 2008 23:26:54 -0400
>> From: Daniel Jacobowitz <drow@false.org>
>> Cc: Vladimir Prus <vladimir@codesourcery.com>,
>> 	gdb-patches@sources.redhat.com
>>
>> It seems to me that the thing to do is eliminate gdb_realpath in favor
>> of lrealpath.  That's supposed to be a portable version of realpath,
>> so realpath semantics seem like the way to go.
>>     
>
> I don't mind doing so, although libiberty has other customers, which
> could make it harder for us to do what we think is right (if it
> happens to be different from what lrealpath does now).  Note that
> right now, lrealpath does not behave consistently with realpath (if
> the latter is unavailable), so it cannot be regarded as a portable
> version of realpath, at least not entirely so.
>   
Most likely libiberty's other customers (read: other GNU components :-) 
) want consistent behavior, and I'm inclined to think they would prefer 
consistency with each other over consistency with "real" realpath. There 
is nothing preventing us from adding additional functions to libiberty 
also, if we want to split functionality in a better way. One maintenance 
bonus of libiberty usage that it forestalls the introduction of subtle 
dependencies on GDB internals, always a hazard with our tangle of headers.

Stan


  parent reply	other threads:[~2008-06-18 15:22 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-14 11:09 Vladimir Prus
2008-06-14 11:30 ` Pierre Muller
2008-06-14 12:14   ` Vladimir Prus
2008-06-14 14:29 ` Eli Zaretskii
2008-06-14 15:10   ` Vladimir Prus
2008-06-14 22:05     ` Eli Zaretskii
2008-06-14 22:26       ` Vladimir Prus
2008-06-15 17:37         ` Eli Zaretskii
2008-06-15 17:43           ` Daniel Jacobowitz
2008-06-15 21:04             ` Eli Zaretskii
2008-06-16  3:17               ` Daniel Jacobowitz
2008-06-16  3:32                 ` Eli Zaretskii
2008-06-18 18:39               ` Stan Shebs [this message]
2008-06-18 20:47                 ` DJ Delorie
2008-06-18 15:22           ` Vladimir Prus
2008-06-18 21:08             ` Eli Zaretskii
2008-06-19  7:27               ` Vladimir Prus
2008-06-20  2:49                 ` Eli Zaretskii

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=4859280A.8000006@earthlink.net \
    --to=stanshebs@earthlink.net \
    --cc=drow@false.org \
    --cc=eliz@gnu.org \
    --cc=gdb-patches@sources.redhat.com \
    --cc=vladimir@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