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

[Danny Smith <dannysmith at clear dot net dot nz>]

----- Original Message -----
From: "Zack Weinberg" <zack@....>

> DJ Delorie <dj@....> writes:
>
> > 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.
>
> Danny, are you happy with me checking in both my patch and yours, and
> worrying about Win9x if and when someone reports a problem?
>

Yes,  please.

> > 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?
>
> I am pretty sure that Windows treats both of those as share names.
>
MSDN uses examples like \\Server\Directory\Filename.
but also says that to qualify for an official Windows logo, an app has
to
support both forward and back slashes in UNC names as well as ordinary
names.
Another requirement is support for  filenames that start with \\?\  and
\\?\UNC\ for
 Unicode'd filenames that exceed MAX_PATH.  (The ? turns off normal path
parsing)

But I'm not too worried about not having a a little Windows logo waving
on the mingw home page.

Note that under windows, UNC names cannot have a filename extension,
like .exe.

Danny
> zw