Go to file
Kp 7b1e774cb8 Hack around buggy clang constant warning
clang whines that static_assert(A && B) uses && with a constant operand,
but this is necessary and correct, because static_assert only takes
compile-time constant expressions.  However, !!A && !!B does not warn.
Switch to !!A && !!B to silence the clang whining.

similar/main/collide.cpp:2566:63: warning: use of logical '&&' with constant operand [-Wconstant-logical-operand]
 static_assert(collision_result_t<OBJ_WALL, OBJ_ROBOT>::value && collision_result_t<OBJ_ROBOT, OBJ_WALL>::value, "OBJ_WALL" " " "OBJ_ROBOT");
2015-06-13 22:42:19 +00:00
common Use fwdvalptridx instead of inline forward declarations 2015-06-13 22:42:16 +00:00
contrib Merge pull #39 into unification/master 2015-06-07 16:21:37 +00:00
d1x-rebirth Make objnum unsigned 2015-06-13 22:42:15 +00:00
d2x-rebirth Use valptr for escort highest_valid 2015-06-13 22:42:16 +00:00
similar Hack around buggy clang constant warning 2015-06-13 22:42:19 +00:00
.gitignore ignore XCode user data 2014-12-06 22:43:12 -08:00
.travis.yml disable non-working clang support in travis 2015-04-25 16:54:05 +00:00
COPYING.txt corrected typo in COPYING.txt (it's to its) 2014-06-06 13:18:52 +02:00
GPL-3.txt
SConstruct Merge pull #39 into unification/master 2015-06-07 16:21:37 +00:00