| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
improper handling of non-ASCII characters by the string pointer lexer
|
|
|
|
comments
|
|
especially never should use
|
|
|
|
|
|
instance variables
|
|
instance variables of SQString into the constructor
|
|
|
|
more explicit
|
|
|
|
|
|
there's no need to construct first and then call init in the next line
|
|
|
|
code from (static) Init to constructure for SQFunctionProto
|
|
|
|
properly initialized
|
|
|
|
|
|
|
|
already in stdafx.h
|
|
|
|
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
|
