Cleaning up legacy code
|This article is a stub. You can help the wiki by|
|FlightGear is an old code base, and lots of the old assumptions (like
a single aircraft) need to be teased out of the code before progress can be made on new features. This kind of work isn't glamorous, and often requires more effort than the new development does. But it's not brain surgery either. The problem with some great new features is that they show up with code that is "ready" to integrate, but without the integration work done. So they languish in the CVS tree until everyone forgets about them. I can recall at least one occasion where a unused module got replaced by a simpler (and arguably less functional) one precicely because the original never got integrated very well and the replacement actually worked.
The extreme programming cult manages to get this idea right (every
religion has a kernal of truth, right?) with their insistence on
constant refactoring and integration. Features are useless in
Legacy OpenGL code
- Andy Ross (Wed, 12 Nov 2003 10:01:42 -0800). Oh where Oh where ........