September 27, 2004 General » Re: UTF-8 char[] consistency | |||
|---|---|---|---|
| |||
...Is it not invalid at least with utf8 to use anything but the least `large... | |||
September 27, 2004 General » Re: UTF-8 char[] consistency | |||
|---|---|---|---|
| |||
...than a class:
struct ICUString {
enum Encoding {UTF8, UTF16, UTF32,...};
uint len;
void* data;
Encoding... | |||
September 24, 2004 Issues » Re: char[] vs. ubyte[] (was: Standard omission or compiler bug: Hexadecimal escapes don't encode into UTF-8) | |||
|---|---|---|---|
| |||
...built-in support as we do for utf8/16/32 then a new type might... | |||
September 23, 2004 Issues » Re: Standard omission or compiler bug: Hexadecimal escapes don't encode into UTF-8 | |||
|---|---|---|---|
| |||
...you had to choose between the types "utf8", "uint8" and "int8", it would be obvious... | |||
September 23, 2004 General » Re: Integer names should be renamed | |||
|---|---|---|---|
| |||
...Let's go /all/ the way... char -> utf8 wchar -> utf16 dchar -> utf32 Then we'll... | |||
September 23, 2004 General » Re: Integer names should be renamed | |||
|---|---|---|---|
| |||
...better than int8. char8/16/32 sounds good, and could also be utf8/16/32 | |||
September 22, 2004 Issues » Re: Standard omission or compiler bug: Hexadecimal escapes don't encode into UTF-8 | |||
|---|---|---|---|
| |||
...the logic of 'defining' char to be utf8 if you're not going to enforce... | |||
September 22, 2004 Issues » Re: Standard omission or compiler bug: Hexadecimal escapes don't encode into UTF-8 | |||
|---|---|---|---|
| |||
...was made impossible to have an invalid utf8/16/32 sequence. That may be an... | |||
September 07, 2004 General » utf-32 text | |||
|---|---|---|---|
| |||
...was the output as if it was UTF8. Did I miss something in the process... | |||
September 03, 2004 General » char[] auto-conversion conflicts with method overloading | |||
|---|---|---|---|
| |||
...of talk regarding additional automatic conversion, between UTF8 and its wchar[] and dchar[] representations. Unfortunately... | |||
Copyright © 1999-2021 by the D Language Foundation