Igor Pechtchanski wrote: > Which was what I said in the part you snipped.
My skimming skills are not great today. :( > > Repeat for "readme" vs. "Readme" and every other of billions of > > permutation of case. I see no way this wouldn't turn into a nightmare. > > Huh? Why would you need to try *all* the permutations? I guess I was conflating the fact that the *current* implementation leaves lower-case and only encodes upper-case / special characters / reserved words with the *proposed* implementation that would have to either encode everything or encode nothing. > Which may or may not be considerable (and no, I don't have measurements to > back it up). There is another overhead, and that is of a human trying to > look at the directory with Windows tools. Yes, encoding is unavoidable, > but it shouldn't be obnoxious. I know it's armchair quarterbacking but it seems to me like urlencoding a filename (requiring no system calls, just string processing) would have a lot less overhead than having to do double the number of calls to CreateFile for nearly every file operation. As far as the human-readable aspect goes, I consider managed mounts as only being required in special or rare circumstances, and so I see having uppercase letters fudged in Explorer is a price one can pay. Don't the majority of filenames consist of lowercase letters anyway? Those would remain untouched to native tools. Brian -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
