On Tue, 8 Jan 2002, Alexandre Julliard wrote:
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.
If you insist... :)
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.
In theory, yes. But you know what Larry McVoy once said:
The difference between theory and practice is that in theory there is no difference, while in practice there is.
Applied to our case, if we have fooW and fooA, then typically fooA looks as such:
fooA() { strdupAtoW fooW strdupWtoA }
So, even if we do go only from A->W at the API level, the actual string conversions do go both ways.
-- Dimi.