Chewing international (unicode) filenames on windows?

[Mark Hammond]

Neil Hodgson wrote:
> 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.

How about just using #include files here then?

>  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.

It doesn't have to be *too* cleanly :)  Having little helper functions 
isn't too bad and could probably work - ie, think "pragmatically" more 
than "cleanly" :)

Mark.