Le 30/4/15 16:07, Guillermo Polito a écrit :
They already are integrated! it's a matter of rewrite all usages of MultiByteScaryStream and friends...
Can you give me just a simple example so that I can understand what has to be done?
El jue., 30 de abr. de 2015 a la(s) 4:06 p. m., stepharo <[email protected] <mailto:[email protected]>> escribió:> I am biased, but the Zn converters are better. Why ? Because they work between String <-> Bytes as a text encoder/decoder should. They also have a number of extra features (counting the number of encoded bytes, being able to move backwards on input, being able to be very strict), are faster and have a clearer implementation. Furthermore, they are more correct and implement more encodings. > > There is also good documentation http://stfx.eu/EnterprisePharo/Zinc-Encoding-Meta/ > > ZnCharacter[Read|Write]Stream are also very instructive, compare them to MultiByteStream. > > Should we throw the other one out ? Probably. But it is the same problems as with Xtreams: the API is different and adding a compatibility layer would defeat the purpose. So I don't know. > > Sven I would integrate the good ones and deprecate the old ones! Stef
