On Thu, Dec 3, 2015 at 11:00 AM, Barret Rhoden <[email protected]> wrote:
> [...]
On occasion, I'm tempted to just switch over completely to the Linux
> style, run checkpatch on the entire code base, and fix it all in one
> fell swoop. The downside is that it'd mess up the git history a bit,
> such that git blame wouldn't be as useful since a bunch of lines are
> getting changed purely for formatting reasons.
>
I could really get behind this; I've seen it done on a few really large
projects now and inevitably it is not nearly as bad as one thinks it will
be: there's sort of one great cataclysmic event in the source history that
folks more or less learn they need to run blame around; it could be
committed with a tag or something that would make it easy to run blame,
diff, or whatever before or after The Great Reformatting of 2015.
The Linux style isn't my personal preference, but I think it's more
important that we have strictness and consistency than that any one style
win over another. But if we're going to do it, I'd give you a whole dollar
and take you to lunch if we moved the return type to a line by itself
before the name of the function (I've never gotten into ctags et al, and
that style makes it easy to use tools like 'grep' to find function
definitions).
- Dan C.
--
You received this message because you are subscribed to the Google Groups
"Akaros" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
For more options, visit https://groups.google.com/d/optout.
