-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Eric Blake on 7/9/2005 2:49 PM:
should this patch be made globally, or should it be limited to only
systems that have a distinct //, leaving other platforms to continue
having just a single slash returned?
Limit it to just those systems,
Eric Blake [EMAIL PROTECTED] writes:
for cross compilation, should I be pessimistic and
make dir_name(//) always return // (unless overridden by priming the
cache, of course)? Or should I write the test with hard-coded knowledge
of the HOST values that are known to have distinct // (so far,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Paul Eggert on 7/9/2005 2:25 PM:
should this patch be made globally, or should it be limited to only
systems that have a distinct //, leaving other platforms to continue
having just a single slash returned?
Limit it to just those
Eric Blake [EMAIL PROTECTED] writes:
Would it be better to patch remove_suffix() to return early if the
name parameter ends in slash (in which case name must have been /
or //), or to patch main() to not even call remove_suffix() in
that case?
The former, I think.
Boy, I really need to get
On Sat, Jul 09, 2005 at 03:43:02PM +, Eric Blake wrote:
POSIX allows implementations to define the behavior of 'basename //' and
'dirname //'. Currently, both operations in coreutils output a single /, but
this definition is worthless on platforms (like cygwin) where // is distinct
from
Eric Blake wrote:
I take it a simple autoconf test is in order (how about just testing
to see if 'ls -di / //' produces 2 different inodes?), and that the
results be used in the gnulib dirname module.
Will that be sufficient? If Cygwin is using this then it might be the
only active system
POSIX allows implementations to define the behavior of 'basename //' and
'dirname //'. Currently, both operations in coreutils output a single /, but
this definition is worthless on platforms (like cygwin) where // is distinct
from /. The intent, according to POSIX, is that 'cd $(dirname string)
[EMAIL PROTECTED] (Eric Blake) writes:
should this patch be made globally, or should it be limited to only
systems that have a distinct //, leaving other platforms to continue
having just a single slash returned?
Limit it to just those systems, please.
I take it a simple autoconf test
[EMAIL PROTECTED] (Eric Blake) writes:
I take it a simple autoconf test is in order (how about just testing
to see if 'ls -di / //' produces 2 different inodes?)
Sounds reasonable.
Why doesn't gnulib use the platform's basename(3) and dirname(3),
They're too often buggy.
