David Megginson writes: > I disagree that this is the biggest obstacle (or even one of the top > 10), but then, I use an editor (XEmacs) with syntax highlighting, > brace matching, language-based navigation (jump forward one function), > etc., so those features might be hiding the problem from me. > > That said, I do agree that this is a problem. We probably need a > standard coding style for FlightGear code, preferably one that is > preinstalled in most programmers' editors. The question is whether we > have anyone with cycles available to lead discussion on this and clean > up the existing code base.
Personally, I've looked, and I've not found any tools that actually do a reasonable job. If we do come up with a style guide it will probably piss off 100% of us. If this is a problem in the top 10, it's definitely not in the top 5. Curt. -- Curtis Olson IVLab / HumanFIRST Program FlightGear Project Twin Cities [EMAIL PROTECTED] [EMAIL PROTECTED] Minnesota http://www.menet.umn.edu/~curt http://www.flightgear.org _______________________________________________ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
