openmw-tes3coop

Commit Graph

Author	SHA1	Message	Date
Douglas Mencken	a3e421167b	esmtool/labels: bodyPartLabel, meshPartLabel, meshTypeLabel Signed chars, unsigned chars... Just use int for index everywhere.	12 years ago
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
cfcohen	68a856ff6f	Human readable labels for many records types. Human readable flags for many record types. Improved DialInfo rule parsing. Discovered several issues involving the assignment of various flag bits.	12 years ago

Author

SHA1

Message

Date

Douglas Mencken

a3e421167b

esmtool/labels: bodyPartLabel, meshPartLabel, meshTypeLabel

Signed chars, unsigned chars... Just use int for index everywhere.

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

cfcohen

68a856ff6f

Human readable labels for many records types. Human readable flags

for many record types.  Improved DialInfo rule parsing.  Discovered
several issues involving the assignment of various flag bits.

3 Commits (cb8d111d36866b7ff98db3d80162f62908e95d45)