This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Import include/filenames.h from BFD (Windows/DJGPP testers needed)


dj@redhat.com (DJ Delorie)  wrote on 02.07.03 in <200307022333.h62NX5K09939@greed.delorie.com>:

> I can't help you test Win9x (don't have any), but the patch looks OK
> syntactically, so if you're happy with whatever testing you end up
> with, I'm ok with you committing it.  I just have one question about
> using \ in argv[0] - what about shares?  If we accidentally end up
> with an argv[0] like "//foo/bar/gcc" vs "\\foo\bar\gcc", will they
> both act like share names, or will one work and not the other?
>
> OTOH, POSIX claims that multiple slashes at the beginning of a path is
> "undefined" so we should probably guard against that anyway.

That is not true.

POSIX says that *two* slashes at the beginning are implementation-defined,  
and more than two are exactly the same as one.

The exception is pretty clearly meant to allow for things like Windows  
share names.

MfG Kai


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]