"Dimitrie O. Paun" dimi@cs.toronto.edu writes:
Excellent. I was not preaching header pollution :). But if we do that, why not have a wine/heap.h header with the said functions?
That's just as much pollution. We must not introduce incompatibilities except where there's clearly no other possibility. In this case there are tons of other options.
Indeed. MultiByteToWideChar is just brutal IMO. But many times if we need to go W->A we also need to go A->W, and hence my proposal for symetrical functions.
The asymmetry could be considered a feature, since people should be encouraged to go A->W instead of W->A wherever possible.