Return-Path: X-Original-To: apmail-flink-dev-archive@www.apache.org Delivered-To: apmail-flink-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id A8AB81037B for ; Mon, 16 Mar 2015 15:57:29 +0000 (UTC) Received: (qmail 13233 invoked by uid 500); 16 Mar 2015 15:57:29 -0000 Delivered-To: apmail-flink-dev-archive@flink.apache.org Received: (qmail 13176 invoked by uid 500); 16 Mar 2015 15:57:29 -0000 Mailing-List: contact dev-help@flink.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@flink.apache.org Delivered-To: mailing list dev@flink.apache.org Received: (qmail 13165 invoked by uid 99); 16 Mar 2015 15:57:29 -0000 Received: from mail-relay.apache.org (HELO mail-relay.apache.org) (140.211.11.15) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 16 Mar 2015 15:57:29 +0000 Received: from mail-vc0-f178.google.com (mail-vc0-f178.google.com [209.85.220.178]) by mail-relay.apache.org (ASF Mail Server at mail-relay.apache.org) with ESMTPSA id 190BE1A02E4 for ; Mon, 16 Mar 2015 15:57:29 +0000 (UTC) Received: by mail-vc0-f178.google.com with SMTP id id10so12473881vcb.9 for ; Mon, 16 Mar 2015 08:57:28 -0700 (PDT) MIME-Version: 1.0 X-Received: by 10.52.237.232 with SMTP id vf8mr15370506vdc.86.1426521448165; Mon, 16 Mar 2015 08:57:28 -0700 (PDT) Received: by 10.52.178.170 with HTTP; Mon, 16 Mar 2015 08:57:27 -0700 (PDT) Received: by 10.52.178.170 with HTTP; Mon, 16 Mar 2015 08:57:27 -0700 (PDT) In-Reply-To: References: Date: Mon, 16 Mar 2015 16:57:27 +0100 Message-ID: Subject: Re: [DISCUSS] Issues with heterogeneity of the code From: Aljoscha Krettek To: dev@flink.apache.org Content-Type: multipart/alternative; boundary=089e013c69282eb848051169e8d0 --089e013c69282eb848051169e8d0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable 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" 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 codi= ng > 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 > wrote: > > > +1 for the stricter Java code styles. > > > > We should not forget about providing code formatter settings for Eclips= e > > 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 : > > > > > > > +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 > > > > wrote: > > > > > > > > > +1 for enforcing a more strict Java code style. However, let's no= t > > > > > introduce a line legth of 100 like in Scala. I think that's hurti= ng > > > > > readability of the code. > > > > > > > > > > On Sat, Mar 14, 2015 at 4:41 PM, Ufuk Celebi > 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 mor= e > > > > > > 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. > > > > > > > > > > > > > > > > > > > > > --089e013c69282eb848051169e8d0--