Chewing international (unicode) filenames on windows?

[Neil Hodgson]

Martin v. Loewis:

> Subclassing may not be the right solution - perhaps it is better to
> admit that ntmodule.c really should be different from
> posixmodule.c. What do you think?

   There is also a lot that should be shared, such as the docstrings, much
of the argument parsing as well as many of the posix calls. Splitting may
lead to more breakage when common patches aren't applied to both.

   Creating a separate file for NT doesn't generalise that well to the many
splits really present in posixmodule, with a quick look showing OS/2, QNX,
SCO and Windows splits along with at least three compilers on Windows
(Microsoft, Borland, Watcom). It needs a way to specify the base generic
posix case cleanly but then to allow platforms to specialise or remove those
functions needing different implementations or which can not be implemented.
In my own C++ work, I normally do this through subclassing.

   Neil