Big Iron Logo Source Forge
PLIB
The Gimp
Mesa 3D Library
Mechanized Combat in the Far Future
Home | News | Features | Screenshots | Download | Contributors | Links

If you're a C++ programmer or you have a good working knowledge of OpenGL or real-time games programming and would like to contribute code, contact the project admin with a brief description of what you know how to do and what you'd like to do. Be sure to check out the ground rules first.

Don't feel like you have to be a super-robo-coding-wizard or anything, this is my first game or 3D project, and the first time I've started a C++ project from scratch.

Even if you're not a coder, we definitely have a need for the following:

If you have any other skills or talents that you think would be useful, let me know and we'll see if we can fit you in somewhere.
As a veteran of large programming projects, I can tell you from experience that consistent coding style is more important than any particular style's merits or flaws. The following are guidelines that I'd like anyone contributing source to follow for new code.

Note: It's okay to leave legacy code (i.e. code reused from another project or source) alone if it's relatively readable.

Files

Identifiers Data Formats Dos and Don'ts And the rest... As far as indentation and bracing goes, use whatever you're comfortable with for new code that you're responsible for. Personally, I prefer 3 space indentation. When you're editting other developers' code, keep your modifications or additions consistent with the original author's style.

Page maintained by Loiosh
Last modified October 09 2002 20:53:04.