I've never gotten warnings doing that before. Maybe it's because I still use the version 6 compiler. But then, it was also faily common practice to use a typedef that was eqivalent to an int, and use corresponding named constants. I don't really know why though.
typedef int BOOL;
const BOOL TRUE = 1;
const BOOL FALSE = 0;
Except, they often used #define instead of const, so it was even more sick.
Well, perhaps we should just define some constants then. Sort of like the Player0 = 0 type constants. Makes identifying the meaning of a parameter in a long list of parameters a lot easier.
You mean like
TethysGame::ForceMoraleRotten(playerAll);
and
TethysGame::CreateUnit(x, mapCommandCenter, LOCATION(64+31, 64-1), player1, mapNone, dirEast);
?
Yeah, that could work.
And thanks, Hooman, for the constant folding