Transport Tycoon Forums

This document is permanently Under Construction.

Transport Empire Prtential Developer Handbook:

1. How to get the source

The Source is available at svn://svn.transportempire.com/trunk/transport_empire_4
Currently it contains only win32, VC10 project and dependancies.


2. How to get the dependancies

TEmpire uses several dependancies to build they include:

Boost - http://www.boost.org/
Ogre - http://www.ogre3d.org

Boost is a gargantuan set of libraries. We actually use only:

3. How to build

TEmpire should port easily to any operating system. Current build however relies on
a few windows specific functions (see timing.h).

Unfortuneatly you have to build yourself a makefile on any platform that is not win32

4. How to submit changes

To submit changes you have to contact our project maintainer - Steve:
http://www.tt-forums.net/memberlist.php ... ile&u=2023

While submitting make sure that the code you have submitted actually
compiles and runs well.

5. General coding tips

Note that TEmpire is a C++ code. This means that it is a template/class/std::
bonanza. Ie you should prefer:

std::string to char*,
std::vector<int> to int[],
cout << "stuff", to printf("stuff")

While nobody will kill you if you use those functions in your own
code - ie inside a class, however when dealing with class interfaces then:

__IT IS STRICTLY FORBIDDEN, UNLESS EXPLICITLY ALLOWED IN SPECIAL
CASES, TO USE C SPECIFIC SOLUTION WHEN C++ SOLUTUION IS AVAILABLE__

This is pretty much the only rule of the project :>

As for formatting your source file, the format is available in template.txt in the source.

6. Reserved for future use

uzurpator wrote: __IT IS STRICTLY FORBIDDEN, UNLESS EXPLICITLY ALLOWED IN SPECIAL
CASES, TO USE C SPECIFIC SOLUTION WHEN C++ SOLUTUION IS AVAILABLE__

Define "C specific solution". Unless you're using class, template, typename, this, public, protected, or private as names (which would be incredibly stupid, and should be forbidden) all valid C code is also valid C++ code. Does this mean that no code that a C compiler would accept is permitted? That will make things ... difficult.

Also:
boost::format vs *printf?
std::vector of boost::any vs va_list et al?

It means:

No void* or void**
No char* for text output
No type[] unless their size is constant (but then boost::array is better)
No defines if template/inline is possible
Avoid globals
no #define value 10 (prefer const int value 10)

all this however is on the module (class) interface. I don't want any ownership or allocation problems between classes. Whatever an author does inside of his class is completely up to him/her

The intent is to ecourage using of modern solutions instead good ol

uzurpator wrote:No char* for text output

So one has to do this: I'm sure I don't have to tell *you* this, but for the benefit of others, "My text\n" is a char*, and sending it direct to cout is clearly using it for output.
Not legal in either C or C++. After applying the obvious corrections, the code is valid in both. What makes this a C++ solution?

DaleStan wrote:

uzurpator wrote:No char* for text output

So one has to do this:

Code: Select all

cout<<string("My text\n"):

I'm sure I don't have to tell *you* this, but for the benefit of others, "My text\n" is a char*, and sending it direct to cout is clearly using it for output.

that is

cout << const char *;

which is a compile time constant. Not a dynamically allocated buffer which is printf'ed/strcmp'ed and there is nothing done to it.
Not legal in either C or C++. After applying the obvious corrections, the code is valid in both. What makes this a C++ solution?[/quote]

Because C programs tend to prefer #define to do A LOT of things, and overuse of macros is dangerous - especially with the lack of namespaces.

well i better get learning C++ haha

Wow! I did it!
Thank for posts and readmes!

ps: see some threads issues..... will fixing
pss: attach to make project actual compile with GCC (ownership_manager for a now disabled )