Official forums for BZFlag.org

Hey everyone,

When ever I download the source code for various files, like bzflag, I check out the source code. I have make a couple of modified clients/servers of bzflag that utilize many more thernary conditionals than are in the standard or cvs versions of the source. I also know many programmers, not just one programmer, makes bzflag, so I know various programmers have various styles of writing or levels of code knowledge. I guess my question is, what I do help edit/organize code for upcoming versions of bzflag, also how would I actually submit my work to you guys. If I didn't mention it before I'm fluent in c/c++, my systems at my home are all AMD64, but its very easy to create 32bit chroots in debian.

Thank You,

I would suggest you log on to the IRC channel #bzflag on irc.freenode.net

This is where most of the developers hang out.

http://my.bzflag.org/w/Google_Summer_of_Code

You might be intrested in the Google Summer of Code: Coding for BZFlag.

This might also answer your question.

Please, by all means, submit code to further BZFlag!

Patches (preferably in unified diff format) may be submitted to the sourceforge patch tracker.

http://sourceforge.net/tracker/?group_i ... tid=303248

If you don't know how to create a patch, please see...hmm, guess we don't have a guide for that yet.

Basically, if you're working off cvs:
cvs diff -u > mypatch.patch
Otherwise, extract a clean (unmodified) copy of the source, and
diff -u /path/to/clean /path/to/modified > mypatch.patch

Note that switching from if-statements to ternary operators is not always a positive change; in most cases, we're more concerned about code readability than performance (though there are plenty of cases where ternary operators are more readable than if-statements).

See also DEVINFO.

ok well thanks for the info guys, I guess I just want to be able to do my part for the community. Oh I do hang out every now and again on the #bzflag channel on freenode, I just keep running out of caffeine to stay there all the time.