I think, if we can all agree that the name is confusing, we should rename it (string_to_utf16 ?) and deprecate the old symbol. Then, in the next stable release it could be removed. When deprecating something compat support needs to be added for previous versions. The Charset module also uses string_to_unicode internally, but I guess it would be possible to move it there.
We had some discussion about development policy during the meeting on the weekend. The intention was to agree on how and in which branches features are removed, APIs made incompatible and new features get added. Bill has the text and will probably make it public soon. The idea is to have a set of guidelines that everyone tries to stick to that make it easier to prepare a stable releases more often. Arne On 12/12/14 06:30, Chris Angelico wrote: > These functions are somewhat misnamed anyway (they convert to UTF-16 > byte streams), and you can always explicitly manipulate UTF-16 using > the Charset.encoder/decoder functions. UTF-8 is far more common, and > the corresponding string_to_utf8/utf8_to_string functions are more > usefully named too. > > Is Pike 8.0 a good time to drop string_to_unicode() and unicode_to_string()? > > ChrisA >
