Tom Tromey <[EMAIL PROTECTED]> writes:
> 2. Is there some document describing the indentation style. I find
> it oddly inconsistent. For instance, synchronized blocks seem to be
> indented differently from everything else. Is this the universal
> Classpath style?
Being a GNU project, we follow the GNU coding standards. Of course
the coding standards are written for C programming, so things diverge
a bit here and there. Aaron's code and mine differs a bit. He
flushes functions to the zeroth column and puts return types on
separate lines. The rational behind aligning return types and
functions on the zeroth column really doesn't apply in the C++ and
Java worlds. In Java, things can especially get ugly if you have
nested classes. Aaron also tends to not put a space after a function
name and the paren.
So we have two styles that are slightly divergent which cover the
majority of the codebase. There's also bits and pieces of code that
were contributed and committed, without ever being stylistically
cleaned up. We've never had strong style guidelines.
I'd personally like to make a conscious effort to move to the style
that matches existing GNU C++ code.
Consistency hasn't been one of our strong points. In the Great
Licensing Change, at least I was able to fix all the copyright lines.
