issue #426 new consistent coding style

[awulder]

Reformatted the code base for an consistent coding/formatting style

[dsaff]

Arjan,

Sorry for the delay in getting to this. Can you find a set of formatting rules that do not create such sweeping changes to long-standing classes like junit.framework.Assert?

[awulder]

David,

Do you have suggestions? I don't think the changes in junit.framework.Assert are that sweeping. Uses spaces instead of tab character, the use of curly brackets, space before and after the equal sign and some blank lines.

[dsaff]

Okay, let's do this in two steps:

Pull 1: create some kind of README file that states the new coding style.
Pull 2: actually commit it.

I agree, on second review, that the changes are none too violent, but I'd like something I can point people to and say: "Please make your code follow these rules." Sounds good?

Sorry for the initial trepidation.

[awulder]

I agree. I will first create a coding style document.

[dsaff]

I apologize: now that the style guide is in, it looks like you'll need to re-apply the style changes. I hope that's not too hard.

[dsaff]

We can close this, right?

[marcphilipp]

I think so, because #522 has been merged. The corresponding issue (#426) is still open, though, because the Eclipse formatter settings are still missing.