evaluation question

Muttley at dastardlyhq.com Muttley at dastardlyhq.com
Wed Feb 1 03:59:17 EST 2023


On Wed, 1 Feb 2023 11:59:25 +1300
Greg Ewing <greg.ewing at canterbury.ac.nz> wrote:
>On 31/01/23 10:24 pm, Muttley at dastardlyhq.com wrote:
>> All languages have their ugly corners due to initial design mistakes and/or
>> constraints. Eg: java with the special behaviour of its string class, C++
>> with "=0" pure virtual declaration. But they don't dump them and make all old
>
>> code suddenly cease to execute.
>
>No, but it was decided that Python 3 would have to be backwards
>incompatible, mainly to sort out the Unicode mess. Given that,
>the opportunity was taken to clean up some other mistakes as well.

Unicode is just a string of bytes. C supports it with a few extra library
functions to get unicode length vs byte length and similar. Its really
not that hard. Rewriting an entire language just to support that sounds a
bit absurd to me but hey ho...




More information about the Python-list mailing list