[PATCH] PR21482: long paths on Windows

[Aaron Ballman]

On Mon, Nov 10, 2014 at 5:36 PM, Robinson, Paul
<Paul_Robinson at playstation.sony.com> wrote:
> My understanding is that CMD.EXE is the one that can't handle them, while
> Explorer actually can.  At least that's what happened to me while I was
> testing this. :-)  But if that's a real concern, then perhaps the better
> approach is to do better at failing when pathnames get too long?  I ran
> into this because a path (not of my own devising) became too long and
> Clang silently failed to do the right thing, for whatever definition of
> "right thing" you care to choose.

Hmm, Explorer may have been updated in more recent versions of Windows. ;-)

I think my preference is to support long file names, and see how bad
the issue is in the wild. If it turns out that this is actually a
painful problem, we can find a way around it. I mostly just wanted to
make sure folks who may not be as used to the quirks on Windows are
aware the issue exists, in case they have stronger opinions than I do.

~Aaron