News for hackers. Stuff that matters.

A comment on Data Processing: PLINQ, Parallelism and Performance. Parent comment

Re:Data Processing: PLINQ, Parallelism and Performance by ori_b on Friday January 07, 2011 @01:09PM (#2080405)
I think you misread - "assures", not "assumes". UTF8 guarantees that any valid ASCII char is NOT part of a UTF8 encoded multibyte char.
[ Parent | on HN ]
Re:Data Processing: PLINQ, Parallelism and Performance by ot on Friday January 07, 2011 @02:46PM (#2080859)
I think you are right.

I thought that the author was meaning that it is possible to use \n and \t in values because UTF8 would encode them in multibyte sequences (like Modified UTF8 encodes \0 as 0xC0,0x80).

What he was actually meaning is that if a codepoint is > 127 its multibyte encoding won't contain any \n or \t.

Sorry for the confusion.

[ Parent | on HN ]