Skip to content

Conversation

@cmb69
Copy link
Member

@cmb69 cmb69 commented Jul 16, 2019

If we have to normalize a path, we always use the canonical path now,
not only when their length differ, since otherwise extended-length
paths could still contain forward slashes, which the file I/O functions
won't handle properly[1].

[1] https://docs.microsoft.com/en-us/windows/win32/fileio/naming-a-file#maximum-path-length-limitation

If we have to normalize a path, we always use the canonical path now,
not only when their length differ, since otherwise extended-length
paths could still contain forward slashes, which the file I/O functions
won't handle properly[1].

[1] <https://docs.microsoft.com/en-us/windows/win32/fileio/naming-a-file#maximum-path-length-limitation>
@cmb69
Copy link
Member Author

cmb69 commented Jul 16, 2019

This change might be too intrusive. I'll take a closer look, and close the PR for now.

@cmb69 cmb69 closed this Jul 16, 2019
@cmb69 cmb69 deleted the fix-78296 branch December 2, 2019 10:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant