Tim Peters <tim.one@comcast.net> writes: > Is this necessarily a different-flavors-of-Windows distinction, or is there > some more fundamental underlying capability that could (and should) be given > an OS-neutral name? There is an abstract underlying capability "supports arbitrary Unicode file names"; the test more specifically relies on the capability "supports those 8 file names being tested". I doubt that this should be given a name at all, be it OS neutral or not. Whatever name you give it, it is likely that the capability will vary across systems, If you take a strict interpretation, you will find that no system supports it (e.g. Windows doesn't allow \ in a file name); if you take a loser definition, you find that all systems support it. > That is, if it's not necessarily a different-flavors-of-Windows > distinction for all time, testing a Windows OS version number isn't > the right answer to this. The test should be run on Win NT (and sons) only. It tests the feature that was just implemented, and that implementation is specific for Windows NT. 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