Yeah, as long as it's in 1 big commit, and you use something like GNU indent, it should be fine even if it is a fair amount of code churn.
On Oct 30, 2012, at 7:21 AM, Kavitha Kumar wrote:
I used the GNU style formatting for the C code. I basically got lazy and used Eclipse to format my code.
And when I did so, I made a separate commit for the formatted code alone so that it was easy to "number" it with svn.
----- Original Message -----
From: "Dominic Hamon" <>
To: "Aaron Brown" <>
Sent: Monday, October 29, 2012 3:36:09 PM
Subject: Re: [ndt-dev] c code style
On Mon, Oct 29, 2012 at 6:48 AM, Aaron Brown < >
On Oct 26, 2012, at 4:10 PM, Dominic Hamon wrote:
Is there an existing code style for the c code in ndt? I noticed that
some of the files seem to have odd wrapping and indenting, but that
might be a mistake due to merging in the past.
I'd like to clean up the code formatting but I don't know what style
As long as it's standardized and easy to reproduce, I don't have a
strong opinion on the matter. My only preference would be to use one
that minimizes the amount of change from the existing scheme (to
avoid unnecessary churn).
I understand. My preference would be the Google C++ style (
which is pretty much what ndt follows, except for the indentation.
I'm happy to fix up the existing code to the style, but I understand
that might be too much change 'just' for formatting. WDYT?
TIP2013, University of Hawaii Mānoa
January 13 - January 17, 2013, Honolulu, HI