On Sun, Feb 10, 2013 at 10:03 AM, Balazs Kelemen <kbal...@webkit.org> wrote:
> On 02/07/2013 01:48 AM, Maciej Stachowiak wrote: > > > I think we should continue to use uint8_t instead of char as the primary > way to represent a raw byte in WebKit. First, it's good to distinguish raw > data from C strings at the type system level, and second, the unpredictable > signedness of char is actively bad for byte-oriented processing. Another > library making a different choice doesn't overcome these reasons. > > > I agree with that, but I still don't see why should LChar be unsigned > since it is a character and not a raw byte. It would be somewhat more > convenient when dealing with string literals or traditional C libraries. I > you agree I could investigate in the refactoring work. > Because LChar is often (always?) UTF-8 encoded, the individual encoding units of which are 0x00 through 0xFF.
_______________________________________________ webkit-dev mailing list webkit-dev@lists.webkit.org https://lists.webkit.org/mailman/listinfo/webkit-dev
