Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Joel Brobecker <brobecker@adacore.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: gcc-patches@gcc.gnu.org, gdb-patches@sourceware.org
Subject: Re: [RFA/libiberty] Fix documentation issues in filename_cmp.c
Date: Fri, 06 Apr 2007 06:10:00 -0000	[thread overview]
Message-ID: <20070406061218.GB3471@adacore.com> (raw)
In-Reply-To: <ud52i4q62.fsf@gnu.org>

Eli,

> > 2007-04-05  Joel Brobecker  <brobecker@adacore.com>
> > 
> >         * filename_cmp.c (filename_cmp): Improve documentation.
> 
> Thanks, I am happy, as far as the documentation goes.

Am I to understand that you are not happy with the code?

You made two comments about the code:

  1. Fold multiple consecutive slash/backslash characters into
     single slash/backslash;

     To do that without modifying the source filenames, we need to
     allocate some memory locally to manipulate a copy of that filename.
     My take on this is that the file names we have seen, at least in
     the debugging information, have been consistent; and thus this
     enhancement would end up having no actual effect. I would wait
     until we come across a case where this is a problem before
     going that way. This is my opinion, and you may disagree...

     Note that this new function does pave the way for this sort
     of enhancement though, and I promise I will not object to a patch
     that implements your suggestion ;-).

  2. The possible introduction of a bug with certain locales because
     the function used in place of strcasecmp uses tolower.

     For this one, as I said, I don't know, and I'm not sure where
     to start looking for the answer. I'll be happy to modify the
     function body to do it any other way, if someone tells me how.

-- 
Joel


  reply	other threads:[~2007-04-06  6:10 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-05 17:27 Joel Brobecker
2007-04-05 18:36 ` DJ Delorie
2007-04-06  6:02   ` Joel Brobecker
2007-04-05 18:44 ` Eli Zaretskii
2007-04-06  6:10   ` Joel Brobecker [this message]
2007-04-06  9:05     ` Eli Zaretskii
2007-04-06 10:00       ` Dave Korn
2007-04-07 17:35       ` Daniel Jacobowitz
2007-04-07 17:52         ` Eli Zaretskii
2007-04-11  7:24           ` Joel Brobecker
2007-04-11 18:28             ` Eli Zaretskii
2007-04-11 20:33               ` Ian Lance Taylor
2007-05-03 15:36                 ` [RFA/libiberty] use TOLOWER instead of tolower " Joel Brobecker
2007-05-03 16:31                   ` Ian Lance Taylor
2007-05-03 23:40                     ` Joel Brobecker
2007-05-04  7:18                   ` Eli Zaretskii
2007-04-11  7:27       ` [RFA/libiberty] Fix documentation issues " 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=20070406061218.GB3471@adacore.com \
    --to=brobecker@adacore.com \
    --cc=eliz@gnu.org \
    --cc=gcc-patches@gcc.gnu.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