It also looks like Google and Sun are mostly the same but designating
'Google' does give us one standard to reference which I like.
That said, Google calls out 2 space indents. Makes it easier to format the
code, but harder to read. Thoughts?
On Sat, Nov 1, 2014 at 8:57 PM, Juiceman wrote:
> T
The tool I am using to convert all the source in a repository is Jindent
which also has the option to sort classes and interfaces, etc.
On Sat, Nov 1, 2014 at 7:00 PM, David ‘Bombe’ Roden wrote:
> Hi there,
>
> initiated by a change in a pull request[1] the issue of coding style (or
> coding sta
On 11/01/2014 07:00 PM, David ‘Bombe’ Roden wrote:
...
> I’m not a big fan of these single large commits that reformat all
> source code at once. As Google’s style guide mandates a little bit
> more than just whitespace and bracket position (e.g. that overloaded
> methods/constructors must not be i
Hi there,
initiated by a change in a pull request[1] the issue of coding style (or coding
standard) popped up, once again. Instead of inventing our own coding style I
proposed on IRC that we used either SUN’s Code Conventions[2] or Google’s Java
Style[3].
Now that I’ve looked for the URL I wou
