Please don't reformat WPILib code during build season

[virtuald]

Originally Posted by kenfox

I'm not sure who is working on WPILib, but it would be very nice if the mid-season releases didn't change source code formatting. I've been trying to keep up with bugs and fixes, but the cosmetic changes make the fixes harder to find.

I'm confused as to why you're keeping up with bugs and fixes? I mean it's great to be aware of them... but if you just don't use the previous version and install the latest binary from them, you're set to go...

[kenfox]

Originally Posted by virtuald

but if you just don't use the previous version and install the latest binary from them, you're set to go...

If we know what changed we can predict how our robot is affected. We can also review previously discarded approaches or learn something new.

On a more personal level, I'd like to be a part of the community. This is an incredible Open Source project with active and inspired development. In order for me to be effective, it's my responsibility to understand the code. I'm asking for a professional courtesy to help make that job easier.

You can see the changes in the latest WPILib here: https://github.com/FRC3322/WPILib/co...688e34f4b13ee1

The green lines are additions; the red lines deletions.

[jwakeman]

After looking at your diff I see that you are just making the point that if (for example) a curly brace is moved from right after the method arguments to the next line it shows up as a difference which makes it more difficult to determine what functionaly changed in the code.

Not sure if you are aware but you can track (and submit) bugs and their fixes on the FIRST Forge site.

http://firstforge.wpi.edu/sf/tracker....wpilib_c_bugs