| Age | Commit message (Collapse) | Author |
|---|
|
|
|
with the same effect
|
|
|
|
|
|
(Windows/OpenTTD) if it exists
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
with gcc3.3 and removes the need of assert_tcompile()
|
|
"non-placement deallocation function [is] selected for placement delete", or in other words delete(void *, size_t) is 'magic'.
We implemented these delete(void *, size_t) operator functions because MSVC warned that "no matching operator delete found; memory will not be freed if initialization throws an exception" for new(size_t, size_t).
This disables MSVC warning about this because we do not use exceptions in the (constructors that use the) overridden allocation functions, as such they will never be called; delete(void *) remains necessary though.
|
|
OTTD's traditional assert_compile() does not work inside templates for gcc compilers, static_assert() does though.
The new assert_tcompile() resolves into static_assert() if present, or into a runtime assert() else.
|
|
CrashLog infrastructure.
|
|
and libpng compiles and links (for me). Something's fishy with the network so it doesn't actually work (yet)
|
|
if available
|
|
I don't have all exotic machines so it might break compilation on the more exotic configurations
|
|
can be reused by other crash logger implementations
|
|
windows does crash reports instead of using several that aren't necessarily equal
|
|
|
|
|
|
|
|
too; no guarantees ofcourse...
|
|
warn when used inside function
|
|
for months. All attempts to do another workaround failed.
|
|
printf-like functions
-Fix: wrong number of parameters or wrong parameter types sent to printf-like functions at several places
|
|
3.1.x Xcodes.
|
|
defining unlink. Also remove redundant tchar.h includes as it is already in stdafx.h.
|
|
file system encoding.
|
|
versions aren't supported anymore. One check in stdafx.h is enough
|
|
compiler doesn't provide the functions promised when that define exists...
|
|
|
|
|
|
false on platforms when S_IFREG is 0x0000.
|
|
|
|
on all platforms
|
|
related errors. Now all error() will 'crash' openttd after showing the message in win32 releases (MSVC), creating a crash.log and crash.dmp (like the '!' hack used before). On the other hand, usererror() will just close the game. So use error() only when it can be helpful to debugging, else use usererror().
|
|
|
|
|
|
declarations.
|
|
something more than whitespace as description of files that don't have a description.
|
|
|
|
always have the NORETURN attribute
|
|
operators.
|
|
math_func.hpp
|
|
|
|
|
