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
..
bsa
compiler
esm	Use `signed char' explicitly where needed. It is important because:	2013-02-15 20:28:14 +01:00
file_finder
fileorderlist
files
interpreter
misc
nif
nifbullet
nifogre
nifoverrides
settings
terrain
to_utf8	Use `signed char' explicitly where needed. It is important because:	2013-02-15 20:28:14 +01:00
translation
CMakeLists.txt
doc.hpp