Tim Peters <tim.one@comcast.net> writes: > Think like a Tim here: what does this test *do*? Currently, the test verifies that a certain piece of C code bracketed by #ifdef MS_WINDOWS works correctly. > Then why is it that Windows NT+ are the only OSes on Earth where > it's possible to do that thing? Testing the Windows code works can work only on Windows, by nature. It so happens that it won't work on W9x, which leaves NT+. > Or are the only OSes on Earth where it's necessary to do that thing? No, users of other systems would want that feature as well. Unfortunately, it can be correctly implemented only on OS X in addition to NT+; a somewhat-flawed implementation would be possible for Unix. > I don't know what FRIENDLY_NAME should be, but "_unicode_file_apis()" > doesn't seem likely to be it. It is really hard to find a precise name, but whatever the answer, it likely contains the words "unicode" and "file (name)". Regards, Martin
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4