Return-Path: Delivered-To: apmail-incubator-esme-dev-archive@minotaur.apache.org Received: (qmail 86183 invoked from network); 12 Nov 2009 12:41:40 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 12 Nov 2009 12:41:40 -0000 Received: (qmail 80305 invoked by uid 500); 12 Nov 2009 12:41:40 -0000 Delivered-To: apmail-incubator-esme-dev-archive@incubator.apache.org Received: (qmail 80255 invoked by uid 500); 12 Nov 2009 12:41:39 -0000 Mailing-List: contact esme-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: esme-dev@incubator.apache.org Delivered-To: mailing list esme-dev@incubator.apache.org Received: (qmail 80245 invoked by uid 99); 12 Nov 2009 12:41:39 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 12 Nov 2009 12:41:39 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of hirsch.dick@gmail.com designates 209.85.218.210 as permitted sender) Received: from [209.85.218.210] (HELO mail-bw0-f210.google.com) (209.85.218.210) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 12 Nov 2009 12:41:32 +0000 Received: by bwz2 with SMTP id 2so2804602bwz.20 for ; Thu, 12 Nov 2009 04:41:11 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:content-type; bh=G8QPeljCCdcaPbs8lYaFDCqmlmnWJAFOcnDE0bQH7cI=; b=e7hl/+wmKJKlRpFH7RFUSSxdgw2DN64BHWujpGdNDioHigrRPVBIKFZAyzuijE9Qyq ARoFqPK9UlGwiKKsfvtaPQgOAysJznob6wgUXmy7Z0VCAHhlAG6Sbt/+IMxAAdX5ei7M clnZPbt8AVWeZuucJVT/vX0/CJeF9iIAXyts8= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=YEo6o0vSCvGXkbdo8Lo6dnD/tC8DbKUVu8tqCCNNtlEKjkTkyyMRB3MwBY8RYMVh6r OYZcSc5dXCU1IE6vSnDR4YjQ/2iJdhAUfOfHYeV+GVHd+0iGQrMoBvZC0kxyL5ydThKS UTeJXV9DxlfQhm1g6GLYQrzx1KPM/m48tvnrc= MIME-Version: 1.0 Received: by 10.103.85.12 with SMTP id n12mr1281826mul.29.1258029671655; Thu, 12 Nov 2009 04:41:11 -0800 (PST) In-Reply-To: References: Date: Thu, 12 Nov 2009 13:41:11 +0100 Message-ID: Subject: Re: Scala style guide From: Richard Hirsch To: esme-dev@incubator.apache.org Content-Type: text/plain; charset=ISO-8859-1 X-Virus-Checked: Checked by ClamAV on apache.org What about doing the formatting in two steps. The first step is automatic and includes dealing with stuff like identing and creating empty method headers. You could probably use existing IDE formatters for that. The second step would be the manual process and would reflect the Style Guide suggestions. D. On Thu, Nov 12, 2009 at 1:30 PM, Vassil Dichev wrote: >> Took a look at the guide and it looks good. The question is: do we >> wait for code beautifier that is based on the guide or do we do format >> our code ourselves? > > I'm not sure there's a non-interactive code beautifier which we can > configure (formatting in IDEs hardcodes many configurations). Besides, > since Scala syntax is still a moving target, I'm not sure anyone has > focused on creating such a beautifier just yet. In a word: we should > format ourselves. > > But a great idea for a hobby project ;-) >