11 Commits (daab4f55a3648a2adfb4f71780909e4b88752efc)

Author	SHA1	Message	Date
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	12 years ago
greye	3494e17b7c	wipe record superclass	12 years ago
greye	721324c1db	rm record inheritance, rework esmtool accordingly	12 years ago
greye	c54750977f	remove underscores in guards	12 years ago
greye	7606ebafd6	resolving conflicts, minor update	12 years ago
Alexander "Ace" Olofsson	0fd48c4229	Extended the esmtool a bit and prepared all records for saving.	13 years ago
Alexander "Ace" Olofsson	ba602929ef	Adding basic save functions to all record types.	13 years ago
Nikolay Kasyanov	fcfe267fc9	Refactored remaining headers in components/esm except defs.hpp. ... Removed obsolete *.cpp files.	14 years ago
Pieter van der Kloet	dd4d022301	Converted all tabs to four spaces	14 years ago
Marc Zinnschlag	6b1b3b20fd	store info records in dialogue records	15 years ago
Marc Zinnschlag	e4f85cb3e6	directory structure reorganisation (still missing the mangle stuff)	15 years ago