* Generate SQL INSERT statements from CSV data for ECM
- REPAIR and BRAIN are still "exceptional" cases requiring syntactical extensions to the DB mini/meta language
git-svn-id: svn+ssh://svn.gna.org/svn/warzone/trunk@6579 4a71c877-e1ca-e34f-864e-861f7616d084
- Don't ignore write(2)'s return value, instead handle it properly to deal with the cases where write(2) gets interrupted (by a signal) or returns prematurely because of non-blocking I/O
- Properly handle popen(3) returning NULL
* Don't assume the data written to stdout by "which" will just fit in our buffer
git-svn-id: svn+ssh://svn.gna.org/svn/warzone/trunk@6577 4a71c877-e1ca-e34f-864e-861f7616d084
* Check for C99 instead of !MSVC where we deal with C99 stuff
* C++98 defines bool as well
* Move BOOL after the bool checks, so we could define it to bool more easily
git-svn-id: svn+ssh://svn.gna.org/svn/warzone/trunk@6572 4a71c877-e1ca-e34f-864e-861f7616d084
Adds weapon range display to the sensor display routine.
Function was split for future enhancements.
This is *not* meant to be played with it enable all the time, as you know, it is a severe resource hog, and it is mainly helpful for modders, to check what the range of the weapons & sensors are.
NOTE: it only shows range for *first* weapon slot.
git-svn-id: svn+ssh://svn.gna.org/svn/warzone/trunk@6566 4a71c877-e1ca-e34f-864e-861f7616d084
An change was introduced on sqlite3_vfs which causes an incompatible
pointer error when mixed with older sqlite versions. Thus bump the
required version to 3.6.10 as well.
git-svn-id: svn+ssh://svn.gna.org/svn/warzone/trunk@6564 4a71c877-e1ca-e34f-864e-861f7616d084
- If it does, check whether it's behaviour is consistent with our implementation
- If behaviour is consistent: use the system's implementation
- If not, rename our implementation (to prevent symbol clashes) and use our own
git-svn-id: svn+ssh://svn.gna.org/svn/warzone/trunk@6556 4a71c877-e1ca-e34f-864e-861f7616d084
- This qualifier allows overriding of CSV field numbers given in base classes
- This is required for the WEAPON stats because it differs from most other stats in that it doesn't have the "designable" field as the last CSV field
* Specify all CSV field numbers for the fields in struct WEAPON
* Generate SQL INSERT statements from weapons.txt
git-svn-id: svn+ssh://svn.gna.org/svn/warzone/trunk@6553 4a71c877-e1ca-e34f-864e-861f7616d084
* It seems that autoconf (2.63 or 2.62) changed the names that are acceptable as custom variable name, and no longer accepts LT_\w+ as variable names.
This addresses #201 and hopefully fixes it.
@EvilGuru, if this fixes it, please close the ticket.
git-svn-id: svn+ssh://svn.gna.org/svn/warzone/trunk@6538 4a71c877-e1ca-e34f-864e-861f7616d084
Make sure we get sucked stronger towards the 2nd waypoint than 1/2 times the strength
we get turned towards the first. Also ensure we get never turned away from a waypoint.
git-svn-id: svn+ssh://svn.gna.org/svn/warzone/trunk@6524 4a71c877-e1ca-e34f-864e-861f7616d084
Since the original assignment probably happened out of confusion what asParts[] shall or shall not contain,
I removed the offending line and added a bit more documentation about that array.
fixes ticket:141
git-svn-id: svn+ssh://svn.gna.org/svn/warzone/trunk@6523 4a71c877-e1ca-e34f-864e-861f7616d084
This reverts commit fbe7a559ee13da78660a68fb69466a46e3d46505.
!!! WARNING: The original issue (clear out of bounds access) is still present in scriptfuncs.c:11467 !!!
git-svn-id: svn+ssh://svn.gna.org/svn/warzone/trunk@6522 4a71c877-e1ca-e34f-864e-861f7616d084
This was used to make AA cannons which originaly aimed at a VTOL not hit anything else
As a speed optimisation we could skip searching the structure list for victims,
if the projectile exploded above the maximum structure height, and do the same for droids
git-svn-id: svn+ssh://svn.gna.org/svn/warzone/trunk@6518 4a71c877-e1ca-e34f-864e-861f7616d084
Per Inge Mathisen
Giel van Schijndel
Guangcong Luo
Buginator
Dennis Schridde
Freddie Witherden