develooper Front page | perl.perl5.porters | Postings from May 2017

Re: Long path names on Windows

Thread Previous | Thread Next
Leon Timmermans
May 9, 2017 07:35
Re: Long path names on Windows
Message ID:
On Tue, May 9, 2017 at 5:11 AM, Zakariyya Mughal <>

> Hello,
> Has there been any progress on supporting long path names on Windows? I
> noticed that there have been changes in Windows 10 that let you opt-in
> to bypassing the `MAX_PATH` limit by setting up a manifest and registry
> key:
> - <>
> - <
> net-4-6-2-and-long-paths-on-windows-10/>
> (spotted on the Python bug tracker <>,
> <>).
> However, it seems that these changes depend on using the wide-char
> versions of the API functions. I see that there is already an issue for
> this here <> (and
> the associated meta issue for Unicode and system calls
> <>).
> If this can not be done yet, it might be useful to catch the error when
> calls like open() fail on Windows. Right now the output of accessing a
> long file path on Windows looks like this:
> ```perl
> use autodie;
> open($long_path);
> ```
> ```output
> Can't open('$long_path'): No such file or directory
> ```
> When I use built-in commands like `dir`, it tells me: `The filename or
> extension is too long.` which is more informative.

I agree this is highly desirable, but it is also rather difficult to
achieve. It would involve both language design challenges and
implementation challenges. I suspect this will require grant work given the
size and scope of it.


Thread Previous | Thread Next Perl Programming lists via nntp and http.
Comments to Ask Bjørn Hansen at | Group listing | About