[Omake] "Strict" case sensitivity.

[Aleksey Nogin]

Hi Jason,

Sorry it took me a while to get back to you on the latest case 
sensitivity stuff (I was sick :-( ).

I have not tried to play with it yet (I should probably do so both under 
Windows and using something like FAT on Linux), but I looked through the 
code of the current implementation and I have a few questions:

- Is there some reason why Omake_cache.ls_exe_path_win32 maps the PATH 
directories to realnames, while ls_exe_path_unix does not?

- Now both Omake_cache_stat and Omake_cache maintain a directory listing 
cache, which seems kind of wasteful - should we merge the two somehow?

- For that matter, the dir_items record field in Omake_cache_stat is 
never used - is it supposed to be?

As far as the "enforced sensitivity" idea itself, I still like it in 
principle and still slightly concerned that we might accidentally 
introduce a lot of strange behaviors where case-sensitive and 
case-insensitive portions of the code [mis]interact in a weird way. On 
the other hand, a while ago we had a somewhat similar case with Cygwin's 
"auto-append .exe to anything, but directory listings" and I think that 
it caused us to be more careful with this...

Is it true that all the fine-in-path, filter-exists and similar 
operations are "strict" in the current implementation? It would seem 
that they need to be, as they are often used to find dependencies in 
some sort of "overinclusive" list.

Aleksey

-- 
Aleksey Nogin, Research Staff Member
Advanced Technologies Department, Information & System Sciences Lab
HRL Laboratories, LLC, Malibu, CA