Erich/openttd - Unnamed repository; edit this file 'description' to name the repository.

Age	Commit message (Collapse)	Author
2009-06-25	(svn r16653) -Fix (r16269): TOC() macro was broken	smatz

2009-06-23	(svn r16637) -Cleanup: remove unused _debug_station_level	smatz

2009-06-01	(svn r16492) -Remove: support for gcc2. It hasn't been able to compile OTTD ↵	smatz
	for months. All attempts to do another workaround failed.
2009-05-10	(svn r16269) -Codechange: use gcc's ability to check parameters sent to ↵	smatz
	printf-like functions -Fix: wrong number of parameters or wrong parameter types sent to printf-like functions at several places
2008-12-29	(svn r14772) -Codechange: make the "dump log of game to reproduce" desync ↵	rubidium
	debug stuff a runtime configurable debug option instead of a compile time option.
2008-11-26	(svn r14634) -Change: _rdtsc is defined by some platforms so we can't use ↵	rubidium
	that name.
2008-07-18	(svn r13728) -Codechange: define DEBUG as an empty block so compiler warns ↵	smatz
	us less
2008-07-18	(svn r13727) -Fix (r13375): compilation with NO_DEBUG_MESSAGES was broken	smatz

2008-06-03	(svn r13375) -Add: logging of actions that could possibly cause desyncs and ↵	smatz
	crashes to simplify debugging. See readme.txt for details
2008-05-06	(svn r12971) -Documentation: add @file in files that missed them and add ↵	rubidium
	something more than whitespace as description of files that don't have a description.
2008-04-13	(svn r12685) -Codechange: DebugDumpCommands() couldn't be inlined, define it ↵	smatz
	as a macro instead
2008-01-24	(svn r11979) -Codechange: drop MSVC 2003 support because MSVC 2003 is broken ↵	rubidium
	in such a manner that it triggers an internal compiler error without any clue what of the code is wrong. Even trying to bisect the problem does not give a single line of code that causes the trouble.
2008-01-11	(svn r11811) -Fix: make compilation without networking work again (and thus ↵	rubidium
	move the debugdumpcommand stuff out of the network 'area').
2007-12-25	(svn r11692) -Codechange: move some functions from 'functions.h' to a more ↵	rubidium
	logical place and remove about 50% of the includes of 'functions.h'
2007-06-08	(svn r10069) -Documentation: some documentation for TIC/TOC, as it isn't ↵	truelight
	what I expected...
2007-03-07	(svn r9050) -Codechange: Foo(void) -> Foo()	rubidium

2007-03-01	(svn r8950) -Cleanup: doxygen changes. Mostly @files missing tags and a few ↵	belugas
	comments style.
2007-02-05	(svn r8605) -Codechange: [OSX] changed all objective C to objective C++	bjarni
	This will permanently solve the issue where compilation on OSX broke because C++ code was added to some header files -Note: (important if you develop mac specific code) taken from http://developer.apple.com/releasenotes/Cocoa/Objective-C++.html gdb lacks an integrated C++ with Objective-C parser. This means that gdb won't be able to evaluate expressions that contain both C++ and Objective-C constructs. gdb assumes that the language for ".mm" files is C++. you can change it to objective C by typing: (gdb) set language objc Mixing C++ and objective C has some limitation (see link for all of them)
2007-01-14	(svn r8124) -Add [DEBUG]: _debug_station_level	KUDr

2007-01-10	(svn r8038) -Merge: the cpp branch. Effort of KUDr, Celestar, glx, Smoovius, ↵	rubidium
	stillunknown and pv2b.
2007-01-02	(svn r7759) -Merge: makefile rewrite. This merge features:	rubidium
	- A proper ./configure, so everything needs to be configured only once, not for every make. - Usage of makedepend when available. This greatly reduces the time needed for generating the dependencies. - A generator for all project files. There is a single file with sources, which is used to generate Makefiles and the project files for MSVC. - Proper support for OSX universal binaries. - Object files for non-MSVC compiles are also placed in separate directories, making is faster to switch between debug and release compiles and it does not touch the directory with the source files. - Functionality to make a bundle of all needed files for for example a nightly or distribution of a binary with all needed GRFs and language files. Note: as this merge moves almost all files, it is recommended to make a backup of your working copy before updating your working copy.