>>>>> "Kon" == Kon Lovett <[EMAIL PROTECTED]> writes:
Kon> Is this a "char-string" issue or a "byte-string"
Kon> issue? When the source "...string..." is a string
Kon> of ASCII non-nul char then there should be no
Kon> problem w/ the utf8 egg overriding the string
Kon> operators. The problem comes when the source "..."
Kon> is actually a "byte-string".
There are other places things can go wrong, of course. If
you use STRING-{SEARCH,MATCH}-POSITIONS, in code that's not
utf8-aware, and any of the match positions come after wide
characters in the string, then it will break if some other
egg has loaded utf8.
This just makes me sad. The whole concept of referencing
strings by index is broken.
--
Alex
_______________________________________________
Chicken-users mailing list
[email protected]
http://lists.nongnu.org/mailman/listinfo/chicken-users
