On 09.07.2014 02:15, Oleg Kolosov wrote:
IMO just enable utf8 by default and let them break. Is it's not 80's
anymore, latin1 only software should die.
+ 1.
For specific use cases (backward compatibility, logging or minimizing
runtime size for example) it should be possible to disable multi-byte
encoding handling (i.e. current behaviour) by using compilation option
or a feature declaration.
+1 again. Let`s remember Python 2.x vs Python 3.x with all that buzz
regarding Unicode support and
how one should tackle with that depending on Python version.
IMHO should we implement UTF-8 in the core and make it a build option
(to disable in cases where
it is really, really not required) will give us totally transparent
support for Unicode to end
users and eggs and eliminate many problems with string processing.
--
Thanks,
Yaroslav
_______________________________________________
Chicken-users mailing list
Chicken-users@nongnu.org
https://lists.nongnu.org/mailman/listinfo/chicken-users
