Re: Handling paths of length > 260 in Tcl on Windows

Thank you, Uwe. From those conversations, I gather the issue is not
yet resolved.

It might be worth adding that interacting with large, complex Java
projects using Tcl as a tool platform requires this kind of support, as
well, as Java uses the extended filename APIs under the Win32 hood, and
some IBM WebSphere tools, as well as Webservice stub generators are all
capable of generating filenames with this problem on any organized
project structure. The varying part of some of those filenames and
paths (the parts that are tool-generated) can, and do, hi 240
characters, forcing us to keep our projects in D:\ if we want them to
be buildable, using Tcl-based tools. This is not a good thing, for
obvious reasons.

Anyway...

I'd like to see this support added in to the core, assuming it's
possible to just pass the names to the underlying routines.

.