Re: [xine-devel] Future of int types in xine

[Michael R. <mr...@us...>]

Hi James,

> > No, it should be "print_dummy(char *text)" here. Whenever there is
> > a string involved, I want to read a "char *" in the code and not
> > some inttype. Strings consist of chars. Period.
> >
> > An array of bytes used for some computation would be a situation,
> > where I would use uint8_t or int8_t.
>
> What about the unichar character set.

You mean unicode, I guess?

> That won't fit into a "char", i think it is a uint16_t, and I don't
> think there is a char16_t.

Well, the widely used UTF-8 encoding can use one to four bytes per 
character, so this cannot be covered with basic types at all. Parsing 
of some form is required here anyway.

Michael

-- 
Those of you who think you know everything are very annoying to those
of us who do.