Gerry Weaver wrote:
> Actually, it was the coding standard document that prompted the question.
Which part of the coding standard, if anything in particular,
raised the question?
I think the standard itself is OK, and in general the code
is fairly compliant. I might be forgetting an old thread.
I myself once brought up the issue of bringing all the code
into compliance, as I'm always thrown by improper indenting.
But it seemed to cause more trouble than it would correct
to do a massive code compliance pass, so I think we do a little
at a time instead.
Esp. now, while 1.3.0 is in development, and we often need
to run diffs against old code to see what changed.
> Although, I think using a program to format the code, even if it were
> to simply abide by the existing standard, would be beneficial.
I'd be more concerned about the massive code diffs
affecting future merges and diffs for the purpose of
code tracking, and detecting regressions.
I often find myself re-formatting code while making mods,
only to later retract those re-format changes to keep the
diffs smaller/simpler, so I can see what code /actually/ changed.
Often code beautifiers make more than just simple white space
changes; long lines will be broken into shorter lines, causing
comments to move around, such that ignoring white space doesn't
make the diffs smaller.
_______________________________________________
fltk-dev mailing list
[email protected]
http://lists.easysw.com/mailman/listinfo/fltk-dev
