- Sep 22, 2020
-
-
Rui Ueyama authored
-
Rui Ueyama authored
-
Rui Ueyama authored
-
Rui Ueyama authored
-
Rui Ueyama authored
-
Rui Ueyama authored
-
Rui Ueyama authored
-
Rui Ueyama authored
-
Rui Ueyama authored
-
Rui Ueyama authored
-
Rui Ueyama authored
-
Rui Ueyama authored
-
Rui Ueyama authored
-
Rui Ueyama authored
-
Rui Ueyama authored
-
Rui Ueyama authored
-
Rui Ueyama authored
-
Rui Ueyama authored
-
Rui Ueyama authored
-
Rui Ueyama authored
-
Rui Ueyama authored
-
Rui Ueyama authored
-
Rui Ueyama authored
-
Rui Ueyama authored
-
Rui Ueyama authored
-
Rui Ueyama authored
-
Rui Ueyama authored
-
Rui Ueyama authored
-
Rui Ueyama authored
-
Rui Ueyama authored
These predefined macros indicates that our u and U chars/strings are UTF-16 and UTF-32-encoded, respectively.
-
Rui Ueyama authored
-
Rui Ueyama authored
-
Rui Ueyama authored
-
Rui Ueyama authored
-
Rui Ueyama authored
-
Rui Ueyama authored
-
Rui Ueyama authored
-
Rui Ueyama authored
-
Rui Ueyama authored
On most Unix-like systems, wide character literal is 32-bit long and encodes a Unicode code point. On Windows, that is 16-bit long and encodes a UTF-16 code unit. Clearly, there's a portability issue here. Personally I've never used wide characters in my code as I didn't find it useful. Being said that, some header files contain wide character literal, so we need to support that so that chibicc can include such files. We assume that source files are always encoded in UTF-8.
-
Rui Ueyama authored
-