trafodion-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Song, Hao-Lin" <>
Subject 答复: Standardize on java code style
Date Fri, 08 Jun 2018 03:24:52 GMT

I think we could standardize our code style from indentation. Now, some old code uses tabs
while some developers uses 3、4 or 8 white spaces as indentation. It is troublesome to align
the format every time, loool.
Beside, 4 white spaces is my favorite because it is neither too long nor too short.

宋昊霖 (Haolin Song)

What doesn’t kill you make you stronger

发件人: Qifan Chen <> 
发送时间: 2018年6月8日 2:23
主题: Re: Standardize on java code style

If we adopt Google style strictly, then there may be differences in naming the class data
members, in a way  not compatible with our C/C++ coding conversion.  For example, we normally
suffix a data member with '_', which is not the case with the Google style, available here  In Google style, the
naming conversion for data members are as follows.

Non-constant field names (static or otherwise) are written in lowerCamelCase.

These names are typically nouns or noun phrases. For example, computedValues or index.

5.2.6 Parameter names

Parameter names are written in lowerCamelCase.

One-character parameter names in public methods should be avoided.

5.2.7 Local variable names

Local variable names are written in lowerCamelCase.

Even when final and immutable, local variables are not considered to be constants, and should
not be styled as constants.

In addition, the # of white space characters to indent a new block of code or a switch statement
is 2, and tabs should not be used to indent blocks etc.

Sounds like we may need to either follow the Google style completely, or follow it in principle
but allow a slight deviation from it, such as suffix data members  with '_'.  I personally
do not use tabs for indentation and put 3 white characters before the start of a new block.

Thanks --Qifan

From: Selva Govindarajan <>
Sent: Thursday, June 7, 2018 11:53:19 AM
Subject: RE: Standardize on java code style

Are there any other guidelines for contributors who use neither of these IDE or any IDE at
all?  In my opinion, 8 spaces seem to be a large indentation that would take the code away
from the screen.  Can these plug-ins be configured with smaller number of spaces.


-----Original Message-----
From: Hans Zeller <>
Sent: Thursday, June 7, 2018 9:29 AM
Subject: RE: Standardize on java code style

+1 on Venkat's proposal.

The Google style seems reasonably compatible with what we have already, both in Java and in

Here are a few guidelines that should help avoiding such large differences, whether we adopt
the Google style or not:

- Don't format entire files, especially not if there is not a common agreed upon style
- Don't insert any tabs into source files (part of Google style)
- For those tabs that unfortunately are in the code, use 8 spaces as the width, as most simple
tools (vi,, emacs, Notepad, BeyondCompare, etc.) do

To Avinash's question: Yes, these are Maven projects.



-----Original Message-----
From: Avinash Dongre <>
Sent: Wednesday, June 6, 2018 10:38 PM
Subject: Re: Standardize on java code style

I have not seen the java code, is it maven based project ??

If java project is converted into gradle, then it has spotless plugin which while building
the code fixes the code style.



From: Venkat Muthuswamy <>
Sent: 04 June 2018 23:56:21
Subject: Standardize on java code style


Given that many contributors are touching same java files and using their own editors of choice,
it becomes difficult to review PRs when git reports large change when mismatch in tabs vs

Can we standardize on the java code style using the google java code style? There are plugins
for eclipse and IntelliJ IDEs.
We start using these on any new files we touch going forward.
GitHub - google/google-java-format: Reformats Java source ...<> google-java-format. google-java-format is a program that reformats Java source code
to comply with Google Java Style.. Using the formatter from the command-line ...

For eclipse, You can download the plugin jar and copy it to your eclipse/drop-ins folder.
Restart eclipse and then set your java formatter implementation to google-java-format in Window
> Preferences > Java > Code Style > Formatter > Formatter Implementation

Comments ?

View raw message