Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Vladimir Prus <vladimir@codesourcery.com>
To: gdb-patches@sources.redhat.com
Subject: Re: Better realpath
Date: Sat, 14 Jun 2008 22:26:00 -0000	[thread overview]
Message-ID: <g3186d$887$1@ger.gmane.org> (raw)
In-Reply-To: <uej6zlrr8.fsf@gnu.org>

Eli Zaretskii wrote:

>> From: Vladimir Prus <vladimir@codesourcery.com>
>> Date: Sat, 14 Jun 2008 16:14:07 +0400
>> Cc: gdb-patches@sources.redhat.com
>> 
>> Speaking of the issues you've raised in:
>> 
>> http://sourceware.org/ml/gdb-patches/2005-05/msg00612.html
>> 
>> I think that:
>> 
>> 1. The order of slashes is a cosmetic issue.
>> 2. The case of filenames is also a cosmetic issues.
> 
> Would it surprise you that I disagree?
> 
> Fixing those is not a big deal, so how about making gdb_realpath
> correct both cosmetically and behavior-wise?

I'm not sure how big deal that is, but it appears we have a major
functionality bug for 3 years already, at least. I'm interested in
fixing that bug, and if somebody (for example you) find those cosmetic
changes important, I think they can be address by follow-up patches.

>> 3. The matter of filename existance is a behaviour issue, and I think
>> I can modify gdb_realpath to perform a check explicitly. OTOH, it's not
>> clear if any code actually expects file existane check to be performed.
> 
> I don't think it matters whether the callers expect it or not.  As
> long as we use realpath, which always checks the result for existence,
> we should do the same in the other branches, so that the resulting GDB
> function behaves consistently.  

If no caller of that function cares about this aspect of behaviour, why
should we bother about consistency. But anyway...

> Alternatively, we could refrain from 
> using realpath, in which case we should consistently _not_ require
> that the file exists.

... as I've said, I can modify gdb_realpath to check for file existance,
on Windows, which will make the behaviour of gdb_realpath the same
everywhere. 

- Volodya



  reply	other threads:[~2008-06-14 20:04 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 [this message]
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
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='g3186d$887$1@ger.gmane.org' \
    --to=vladimir@codesourcery.com \
    --cc=gdb-patches@sources.redhat.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