Douglas Mencken df5919f2c5 Use `signed char' explicitly where needed. It is important because: ... - It is implementation-dependent if plain `char' signed or not. - C standard defines three *distinct* types: char, signed char, and unsigned char. - Assuming that char is always unsigned or signed can lead to compile-time and run-time errors. You can also use int8_t, but then it would be less obvious for developers to never assume that char is always unsigned (or always signed). Conflicts: components/esm/loadcell.hpp		2013-02-15 20:28:14 +01:00
..
tests	to_utf8 test: fix Utf8Encoder constructor	2013-01-06 11:39:18 +01:00
.gitignore	Added custom UTF8 converter. Removed iconv dependency.	2010-08-18 18:45:44 +02:00
gen_iconv.cpp	Update UTF 8 table generator to print char values	2012-08-27 10:55:39 -04:00
Makefile	Mantis: #18 - Move components from global namespace into their own namespace.	2011-06-19 19:33:30 +02:00
tables_gen.hpp	Use `signed char' explicitly where needed. It is important because:	2013-02-15 20:28:14 +01:00
to_utf8.cpp	Use `signed char' explicitly where needed. It is important because:	2013-02-15 20:28:14 +01:00
to_utf8.hpp	Use `signed char' explicitly where needed. It is important because:	2013-02-15 20:28:14 +01:00