Re: More elegant UTF-8 encoder



Stephen Sprunk wrote:

.... snip ...

While I'll grant it's unlikely, it's indeed _possible_ that the
limit will be lifted in the future. Since UTF-8 follows a
consistent pattern up to seven octets, there's no reason not to
allow for encoding or decoding it as long as it's well-formed.
The UCS-2 folks all got burned when UTF-16 came out with its
surrogates, remember, and it didn't even take that long; I don't
plan on repeating their mistakes. Just like I never thought
640kB RAM (or 4GB) was enough for everybody and allowed for more
if/when it became possible...

Hell, back in '78 I proposed a system with the outrageous memory
addressing capacity of 24 bits, or 16 Megs. Who could possibly
need (or afford) more. It also provided for 16 bit words.
Published in DDJ.

--
<http://www.cs.auckland.ac.nz/~pgut001/pubs/vista_cost.txt>
<http://www.securityfocus.com/columnists/423>
<http://www.aaxnet.com/editor/edit043.html>
<http://kadaitcha.cx/vista/dogsbreakfast/index.html>
cbfalconer at maineline dot net



--
Posted via a free Usenet account from http://www.teranews.com

.



Relevant Pages

  • Re: w regular expressions unicode
    ... can however make them parsed (provided they are valid UTF-8). ...    treated as being part of a literal UTF-X sequence. ... The utf8 pragma affects the whole file, ...
    (perl.beginners)
  • Re: Just how delicate are freed pointers?
    ... snip ... ... it's valid on some implementations and allowed by the ... |>>> Standard. ...
    (comp.lang.c)
  • Re: Power tilt problem
    ... In article, princecraft51 ... snip... ... He cared so little for his ailing dad that he wouldn't grant Inky's last ...
    (rec.boats)
  • Re: Power tilt problem
    ... In article, princecraft51 ... snip... ... He cared so little for his ailing dad that he wouldn't grant Inky's last ...
    (rec.boats)
  • Re: Power tilt problem
    ... In article, princecraft51 ... snip... ... He cared so little for his ailing dad that he wouldn't grant Inky's last ...
    (rec.boats)