On 2011-09-28 21:56, Jonathan M Davis wrote:
Having toUTF and toUTFz is a marked improvement in many cases - especially for
generic code. They're being added regardless of what the deal with toUTF16z
is.
The reason that toUTF16z is being removed is essentially because Andrei is
very much opposed to having functions with specific types in their names and
thinks that they should all be generic. Personally, I'm not opposed to keeping
toUTF16z as an alias or wrapper to toUTFz. It's Andrei that seems to feel
stongly about it. So, if enough people really want to keep toUTF16z, then I
think that that can happen.
Seems a bit arbitrary what gets deprecated with the old API left in
place and what gets deprecated with the old API removed.
--
/Jacob Carlborg
