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
..
.gitignore	Moved esmtool to apps/	2010-07-21 13:52:28 +02:00
CMakeLists.txt	Human readable labels for many records types. Human readable flags	2012-10-10 22:00:44 -04:00
esmtool.cpp	Merge remote-tracking branch 'upstream/master' into multiple_esm_esp	2013-01-25 18:22:01 +01:00
labels.cpp	Use `signed char' explicitly where needed. It is important because:	2013-02-15 20:28:14 +01:00
labels.hpp	Use `signed char' explicitly where needed. It is important because:	2013-02-15 20:28:14 +01:00
record.cpp	post merge fix	2012-12-18 12:36:26 +01:00
record.hpp	Remove tabs as requested. Sorry about that, thought I already	2012-10-09 19:41:45 -04:00