Difference between revisions of "C plus plus version"
From WikiManual
(→C++ coding standards) |
|||
| Line 1: | Line 1: | ||
| − | + | Original document (and comments) by Taldor in black, comments by Numsgil in <font color="Red">Red</font>. | |
| − | + | I propose we discuss the C++ design and coding standards in here. A wiki is much handier then a forum or PM's for it.--[[User:Taldor Taldor]] | |
| + | |||
| + | == Language switch == | ||
| + | |||
| + | You wonder why we're switching? Because VB is for simple, gui based programs. Darwinbots is nor a simple program, nor gui based. In contrary C++ is a powerfull language, but it has a higher development cost. | ||
== C++ design == | == C++ design == | ||
| Line 14: | Line 18: | ||
* Main | * Main | ||
| − | ** | + | ** User Interface ([http://www.fox-toolkit.org Fox Toolkit]) |
| − | *** | + | *** Simulation sub window (3D - [http://www.opengl.org OpenGL]) |
| − | + | ** Darwin (the simulation engine) | |
| − | + | *** Veg | |
| − | + | *** Tie | |
| − | + | *** Robot | |
| − | + | **** Sense | |
To be used everywhere: | To be used everywhere: | ||
| Line 42: | Line 46: | ||
# [http://www.cppreference.com C/C++ Reference] | # [http://www.cppreference.com C/C++ Reference] | ||
# [http://www.parashift.com/c++-faq-lite C++ FAQ Lite] | # [http://www.parashift.com/c++-faq-lite C++ FAQ Lite] | ||
| + | # [http://en.wikipedia.org/wiki/Visual_basic#Controversy Visual Basic controvercy] | ||
Revision as of 17:12, 30 October 2005
Original document (and comments) by Taldor in black, comments by Numsgil in Red.
I propose we discuss the C++ design and coding standards in here. A wiki is much handier then a forum or PM's for it.--User:Taldor Taldor
Contents
Language switch
You wonder why we're switching? Because VB is for simple, gui based programs. Darwinbots is nor a simple program, nor gui based. In contrary C++ is a powerfull language, but it has a higher development cost.
C++ design
General concepts
- Class based approach. In some cases, procedural in others. It's a value decision I'll make as I port the code.
- Portable code. Where possible. Preferably in house or free library wrappers for non portable functions, such as multithreading and OS timers.
Structure
See the present VB code
- Main
- User Interface (Fox Toolkit)
- Simulation sub window (3D - OpenGL)
- Darwin (the simulation engine)
- Veg
- Tie
- Robot
- Sense
- User Interface (Fox Toolkit)
To be used everywhere:
- Vector_4 (using uBLAS) Present vector class is from this article. I'll use whichever is fastest, feel free to perfrom benchamrks
- Matrix_4 (also using uBLAS) See above
- Random (using 'srand()' and 'rand()') See the chapter on random numbers
- Object (the base class) Depends on the class
C++ coding standards
I would use:
- C++ C++ libraries where such libraries do what I want them to do, C libraries otherwise. Another value decision. All C librairies are included in C++. Mixing C and C++ isn't the easiest task, however OO C++ and procedural C++ can be mixed easily. I agree, but I've been having some trouble with various C++ libraries that immediatly goes away when I switch to the C versions. Might just be my compiler MSVC++ 6.0
- Four spaced tabs - Aye.
- External librairies when possible (ie. Boost) Internal libraries where possible, to decrease the number of code dependancies, except where external libraries perform the job faster/more comoprehensively than internal libraries can.
- SDL Dunno, haven't looked into graphics libraries yet.
- ...
