| Age | Commit message (Collapse) | Author |
|---|
|
|
|
that followed
|
|
Clang-cl presents as both _MSC_VER and __clang__ in the preprocessor which makes some things confusing.
|
|
CMake works on all our supported platforms, like MSVC, Mingw, GCC,
Clang, and many more. It allows for a single way of doing things,
so no longer we need shell scripts and vbs scripts to work on all
our supported platforms.
Additionally, CMake allows to generate project files for like MSVC,
KDevelop, etc.
This heavily reduces the lines of code we need to support multiple
platforms from a project perspective.
Addtiionally, this heavily improves our detection of libraries, etc.
|
|
|
|
(fixes warning from clang)
|
|
|
|
This can avoid out-of-memory situations due to single scripts using up the entire address space.
Instead, scripts that go above the maximum are killed.
The maximum is default 1 GB per script, but can be configured by a setting.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
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
|
|
error, due to the stack to throw the error already being full
|
|
data via a looping set of references
|
|
a script
|
