Re: [Chicken-users] ditching syntax-case modules for the utf8 egg

[John Cowan]

Tobia Conforto scripsit:

> This is more or less how other languages, such as Python, solved the  
> issue.  Two kinds of strings, byte and unicode, and overloading a few  
> string operations to have a slightly different meaning when called on  
> either, computing byte length vs. character length.

And Python 3.0 is ditching this solution in favor of byte strings
and Unicode strings instead, because it's unworkable in the long run.
In Py3k, you'll write b"..." for a byte string and "..." for a Unicode
string; u"..." will be a deprecated synonym.  Python 2.6, the bridge
release, will support b"..." to assist transition.

-- 
John Cowan              address@hidden          http://www.ccil.org/~cowan
Historians aren't constantly confronted with people who carry on
self-confidently about the rule against adultery in the sixth amendment to
the Declamation of Independence, as written by Benjamin Hamilton. Computer
scientists aren't always having to correct people who make bold assertions
about the value of Objectivist Programming, as examplified in the HCNL
entities stored in Relaxational Databases.  --Mark Liberman