[ODE] Code quality

[Dave Grundgeiger]

> Remi Ricard wrote:
>> But before doing that we need a standard.

Jon Watte wrote:
> You could look at joint.cpp (to take a representative file), figure out 
> what the main prevailing standard in that file is, and come up with an 
> astyle set of parameters that captures as much of this as you can. Then 
> post it to the list, and assume all submissions will be formatted 
> according to this. Given that astyle is easy to run, someone could even do 
> that periodically to the source.

I can volunteer for this. It's an easy way for a newbie to contribute 
something.

> Formatting just isn't worth the argumentation time. Let's solve it 
> automatically and move on to what counts: quality and test standards.

Exactly!