33 ms·
> The two most visible warts - CRLF and '\' - are the ones to watch for when they get deprecated. There's a third wart, the path length limit of 260 characters
by cesarb 6y ago
> The two most visible warts - CRLF and '\' - are the ones to watch for when they get deprecated.
There's a third wart, the path length limit of 260 characters. Work on that seems to already be in progress: https://docs.microsoft.com/pt-br/archive/blogs/jeremykuhne/net-4-6-2-and-long-paths-on-windows-10 https://docs.microsoft.com/pt-br/archive/blogs/jeremykuhne/n... (though I see no mention of a related and more annoying wart, which is not allowing some simple file names like "aux.c").
- WorldMaker 6y agoYou can always use \\?\ namespace paths to get above the 260 character limit, just not all Win32 applications can work with those files. Don't expect AUX, COM1, etc to be fixed any time soon, because that is a huge backwards compatibility issue.
- captainmuon 6y ago> Don't expect AUX, COM1, etc to be fixed any time soon, because that is a huge backwards compatibility issue. I think that this is also possible to fix. Always require the colon ('CON:' instead of 'CON'), and make this opt-in per process, like "longPathAware". Sure, old apps will choke if you now create a CON file. But 1) the file dialogs could show a warning when doing that, 2) you can already create filenames that make old apps choke and 3) they could transparently show them as CON~1 or something in those old apps.
- ygra 6y agoA warning wouldn't really fix much for most people. »This file name might potentially not work in certain applications« is far too vague for anyone to determine whether it's a good idea to name the file that way or not. And erring on the side of caution brings you to the same situation as right now that you better avoid those names. For the dedicated there's a way to create them anyway, and many power user tools allow you to create and handle them.