Go to file
Kp 08e4a6e620 Use stdint constants for some INT*_MAX
clang becomes confused trying to determine which vm_distance_squared
constructor to use for a literal input of 0x7fffffffffffffff, even
though the size of the input requires it to be `long` and only one
constructor can take a `long`.  Switch from an explicit
0x7fffffffffffffff to the symbolic constant INT64_MAX, which has the
same value, but a platform-appropriate suffix to force the compiler to
pick the right type.

For general clarity, switch some other instances of integer maximum
literals to symbolic constants of the same value.

This commit has no effect on the generated code (except for changes to
line numbers).

Reported-by: kreatordxx <https://github.com/dxx-rebirth/dxx-rebirth/pull/324>
Fixes: 17208cca79 ("Disallow int for vm_distance_squared")
2017-02-22 03:05:43 +00:00
common Use stdint constants for some INT*_MAX 2017-02-22 03:05:43 +00:00
contrib Update Xcode project for recently added/removed files 2017-01-07 15:30:18 +08:00
d1x-rebirth Simplify redundant ehostage.cpp conditional 2017-02-08 23:34:41 +00:00
d2x-rebirth Never pass nullptr to ai_door_is_openable 2017-02-19 19:33:45 +00:00
Documentation Require support for reference qualified methods 2016-12-10 17:51:07 +00:00
similar Use stdint constants for some INT*_MAX 2017-02-22 03:05:43 +00:00
.gitignore
COPYING.txt
GPL-3.txt
INSTALL.markdown Fix Ubuntu package name in INSTALL.markdown 2016-12-23 02:56:55 +00:00
SConstruct Fix check_header_includes=1 poison.h 2017-02-19 19:33:36 +00:00