News for hackers. Stuff that matters.
Re:Mercurial’s journey to and reflections on Python 3 by simias on Monday January 13, 2020 @06:06PM (#22039761)
Not to mention case-sensitivity issues. Can you have two files, one named "FILE.txt" and the other "file.txt" in the same directory for instance?
Re:Mercurial’s journey to and reflections on Python 3 by SSLy on Monday January 13, 2020 @06:40PM (#22040043)
On windows? Of course you can.
Re:Mercurial’s journey to and reflections on Python 3 by edgyquant on Monday January 13, 2020 @07:53PM (#22040639)
I'm certain you can on Linux as well. Only Macs old HFS would not allow it.
Re:Mercurial’s journey to and reflections on Python 3 by cataflam on Monday January 13, 2020 @08:10PM (#22040741)
Isn't this a fairly recent change?
Re:Mercurial’s journey to and reflections on Python 3 by amaranth on Tuesday January 14, 2020 @12:18AM (#22042070)
NTFS has always been case sensitive, Windows API just lets you treat it as case insensitive. If you pass `FILE_FLAG_POSIX_SEMANTICS` to `CreateFile` you can make files that differ only in case.
Re:Mercurial’s journey to and reflections on Python 3 by mathw on Tuesday January 14, 2020 @03:56AM (#22043009)
Good luck using those in some tools which use the API differently though. Windows filenames are endless fun. What's the maximum length of the absolute path of a file? Why, that depends on which API you're using to access it!
Re:Mercurial’s journey to and reflections on Python 3 by rurban on Wednesday January 15, 2020 @12:39AM (#22052001)
Even worse on Unix where it depends on the mount type. Haven't seen much proper long filename support in Unix apps or libs, it's much better in Windows land. Garbage in garbage out is also a security nightmare as names are not identifiable anymore. You can easily spoof such names.