Mailing-List: contact dev-help@flink.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@flink.apache.org
MIME-Version: 1.0
In-Reply-To: 
 <CANMXwW3cJ5y490x5RmnjcPNGFtrCde=ff2_nJgODOzA+WTrqPA@mail.gmail.com>
References: 
 <CANC1h_voN0B5omNWZxcHTyzwHAKeGhbZVQUyK7S9o2A36b891Q@mail.gmail.com>
	<CCECF572-3215-4F69-84F0-9FEE3EBB6CEC@apache.org>
	<CAC27z=ONOakCib9Oo9iy-yqgmagES0ANcaeesJ0vYYNPu9VV9w@mail.gmail.com>
	<CALuGr6bKbbkaRvkgapjwKhw4cdSUyAf5hno-Ned3baGHQ4DZRQ@mail.gmail.com>
	<CANC1h_t0xTGrBpj_0z4AjHoa0X-L=jMkjRtnObNx0LrLsPjTnQ@mail.gmail.com>
	<CALuGr6ZPE2cUyu1COhtN8v6y4YaER9j94jicQz4huXomyEWT9g@mail.gmail.com>
	<CAAdrtT0Cw+=7jzL-==KnJTrO=kguob2OVSh67fFKkGAU4rGK5w@mail.gmail.com>
	<CALuGr6YM5UFRvyBqKBsh7gyE+a=JYGzgHfL2gWyQCmhH--85GA@mail.gmail.com>
	<CANMXwW2OMQABYHeFBYkCX+03c3J5N-c-4zhKZOpi=JnayH0z7Q@mail.gmail.com>
	<CAKiyyaEO+gvwq8mTkec_b-EDwDLGZdx6_Lu3nisyL3VVuGbXeQ@mail.gmail.com>
	<CAGco--bTy3LRJU+XUTk6mLH5jaS_DTCOtXEVRZd2B=xQ=xxGjg@mail.gmail.com>
	<CANC1h_u2Y+xqRt_3dP+bJ6yq5ZQv_znVcd5=CxbktS+v+Kwhiw@mail.gmail.com>
	<CAEXqXcYbLeFBb3vXrf1ajKCM0wMMuCjNU=8dXxGFEfpx4N761A@mail.gmail.com>
	<CAF6bXwWnGznVSA35GrXehrB6fNAp1oRhn6dwB_LT6EjTak1MJA@mail.gmail.com>
	<CAC27z=P7-a+4h=3RvDUG2s_eL0n8YMGU2FCRwmAzb105biuJ2Q@mail.gmail.com>
	<CANMXwW3cJ5y490x5RmnjcPNGFtrCde=ff2_nJgODOzA+WTrqPA@mail.gmail.com>
Date: Mon, 16 Mar 2015 17:37:05 +0100
Message-ID: 
 <CAC27z=PyYep4zSj4fY2fFq4vDSOJBV=0t=MPrD6EjZVxhTcXAQ@mail.gmail.com>
Subject: Re: [DISCUSS] Issues with heterogeneity of the code
From: Till Rohrmann <trohrmann@apache.org>
To: dev@flink.apache.org
Content-Type: multipart/alternative; boundary=001a1135510cdbd52205116a7501

--001a1135510cdbd52205116a7501
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Do we already enforce the official Scala style guide strictly?

On Mon, Mar 16, 2015 at 4:57 PM, Aljoscha Krettek <aljoscha@apache.org>
wrote:

> I'm already always sticking to the official Scala style guide, with the
> exception of 100 line length.
> On Mar 16, 2015 3:27 PM, "Till Rohrmann" <trohrmann@apache.org> wrote:
>
> > +1 for stricter Java code styles. I haven't looked into the Google Code
> > Style but maybe we make it easier for new contributors if we apply a
> coding
> > style which is somehow known.
> >
> > +1 for line length of 100 for Scala code. I think it makes code review =
on
> > GitHub easier.
> >
> > For the Scala style, we could stick to official style guidelines [1].
> >
> > [1] http://docs.scala-lang.org/style/
> >
> > On Mon, Mar 16, 2015 at 3:06 PM, Hermann G=C3=A1bor <reckoner42@gmail.c=
om>
> > wrote:
> >
> > > +1 for the stricter Java code styles.
> > >
> > > We should not forget about providing code formatter settings for
> Eclipse
> > > and Intellij IDEA (as mentioned above).
> > > That would help a lot.
> > >
> > > (Of course if we'll use Google Code Style, they already provide such
> > files
> > > <
> > >
> >
> https://code.google.com/p/google-styleguide/source/browse/trunk/intellij-=
java-google-style.xml
> > > >
> > > .)
> > >
> > > On Mon, Mar 16, 2015 at 2:45 PM Alexander Alexandrov <
> > > alexander.s.alexandrov@gmail.com> wrote:
> > >
> > > > +1 for not limiting the line length.
> > > >
> > > > 2015-03-16 14:39 GMT+01:00 Stephan Ewen <sewen@apache.org>:
> > > >
> > > > > +1 for not limiting the line length. Everyone should have a good
> > sense
> > > to
> > > > > break lines. When in exceptional cases people violate this, it is
> > > usually
> > > > > for a good reason.
> > > > >
> > > > > On Mon, Mar 16, 2015 at 2:18 PM, Maximilian Michels <
> mxm@apache.org>
> > > > > wrote:
> > > > >
> > > > > > +1 for enforcing a more strict Java code style. However, let's
> not
> > > > > > introduce a line legth of 100 like in Scala. I think that's
> hurting
> > > > > > readability of the code.
> > > > > >
> > > > > > On Sat, Mar 14, 2015 at 4:41 PM, Ufuk Celebi <uce@apache.org>
> > wrote:
> > > > > >
> > > > > > > On Saturday, March 14, 2015, Aljoscha Krettek <
> > aljoscha@apache.org
> > > >
> > > > > > wrote:
> > > > > > >
> > > > > > > > I'm in favor of strict coding styles. And I like the google
> > > style.
> > > > > > >
> > > > > > >
> > > > > > > +1 I would like that. We essentially all agree that we want
> more
> > > > > > > homogeneity and I think strict rules are the only way to go.
> > Since
> > > > this
> > > > > > is
> > > > > > > a very subjective matter it makes sense to go with something
> > > > (somewhat)
> > > > > > > well
> > > > > > > established like the Google code style.
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
>

--001a1135510cdbd52205116a7501--