| Age | Commit message (Collapse) | Author |
|---|
|
|
|
exporting things to C from our squirrel
|
|
|
|
well, and prevent using the ones that are deemed unsafe
|
|
defines
|
|
|
|
|
|
everything non-Windows or non-Unicode, now everything), the lexer throws away the higher bytes of characters
|
|
platforms having wchar for SQChar and others just char; always use char (and UTF-8) like in the rest of (internal) OpenTTD
|
|
|
|
assigning values to variables with smaller integer size
|
|
always 64 bits, so scripts behave the same on 32 or 64 bits architectures
|
|
"unsafe" functions to prevent them from being used, and thus having to care about certain aspects of their return values
|
|
|
|
error, due to the stack to throw the error already being full
|
|
data via a looping set of references
|
|
a script
|
|
processing 'while' token of 'do'-'while' statement.
|
|
with negative size
|
|
wasn't caught properly, so they could cause crashes of OpenTTD instead of the AI
|
|
|
|
machines failed
|
|
others were still regular inline), but make sure inline is always a 'forced' inline (I am looking at you MSVC)
|
|
meta-function doesn't return an integer
|
|
it mostly solves the sort() issues
|
|
|
|
included file
|
|
|
|
fix stack overflow
|
|
|
|
|
|
the squirrel compiler to crash
|
|
difference was more than "MAX_UINT"/2
|
|
the AI debug window, use the relative path from /ai/ instead
|
|
|
|
using MSVC update openttd-useful, otherwise make sure you've got liblzo2 and it's development files installed.
|
|
-Revert (r17273): this fix is included in Squirrel 2.2.4
|
|
I've never heard of)
|
|
|
|
|
|
|
|
not be cleaned up properly during crash handling. Occasionally this causes asserts to be triggered or crashes.
|
|
warning about them
|
|
|
|
assert is enabled assert (catch possible overflow bugs in nightlies/RCs), otherwise just increase the stack's size (don't get into invalid reads/writes in releases)
|
|
tail recursion
|
|
|
|
|
|
with not enough parameters can cause a crash
|
|
3rdparty directory.
|
