raze-gles/polymer/eduke32/source/xdelta3
terminx 3ff46c02b2 Fix the warnings when building with C++, add MSVC C++ build support. This also changes the internal type of lotags, hitags and cstat type fields to uint16_t instead of int16_t to clean up some dubious behavior wherein the code was using a value of 32768 as a flag in these fields for certain types of things, like invisible sprites (using the value as if it was uint16_t) where it was elsewhere checking if the value was < 0 (using the value as if it was int16_t). This change may break a few specific effects if any part of the relevant code was missed when looking for areas that needed to be addressed.
I think there's also a fix for the CON precache system breakage in here (lost it in my local tree when I started getting the C++ build working in MSVC, sorry!)


git-svn-id: https://svn.eduke32.com/eduke32@3159 1a8010ca-5511-0410-912e-c29ae57300e0
2012-11-14 23:32:43 +00:00
..
xdelta3-cfgs.h Add xdelta3, required for some broken multiplayer updates I plan on committing later 2012-05-17 21:27:19 +00:00
xdelta3-decode.h Update xdelta3 to 3.0.4. I haven't actually tested these changes yet but they're directly from upstream. 2012-10-15 16:13:13 +00:00
xdelta3-hash.h Update xdelta3 to 3.0.4. I haven't actually tested these changes yet but they're directly from upstream. 2012-10-15 16:13:13 +00:00
xdelta3-internal.h Update xdelta3 to 3.0.4. I haven't actually tested these changes yet but they're directly from upstream. 2012-10-15 16:13:13 +00:00
xdelta3-list.h Add xdelta3, required for some broken multiplayer updates I plan on committing later 2012-05-17 21:27:19 +00:00
xdelta3.c Update xdelta3 to 3.0.4. I haven't actually tested these changes yet but they're directly from upstream. 2012-10-15 16:13:13 +00:00
xdelta3.h Fix the warnings when building with C++, add MSVC C++ build support. This also changes the internal type of lotags, hitags and cstat type fields to uint16_t instead of int16_t to clean up some dubious behavior wherein the code was using a value of 32768 as a flag in these fields for certain types of things, like invisible sprites (using the value as if it was uint16_t) where it was elsewhere checking if the value was < 0 (using the value as if it was int16_t). This change may break a few specific effects if any part of the relevant code was missed when looking for areas that needed to be addressed. 2012-11-14 23:32:43 +00:00