Return-Path: Delivered-To: apmail-incubator-esme-dev-archive@minotaur.apache.org Received: (qmail 45252 invoked from network); 24 Oct 2009 20:26:52 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 24 Oct 2009 20:26:52 -0000 Received: (qmail 20763 invoked by uid 500); 24 Oct 2009 20:26:52 -0000 Delivered-To: apmail-incubator-esme-dev-archive@incubator.apache.org Received: (qmail 20713 invoked by uid 500); 24 Oct 2009 20:26:52 -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 20703 invoked by uid 99); 24 Oct 2009 20:26:52 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 24 Oct 2009 20:26:52 +0000 X-ASF-Spam-Status: No, hits=-2.6 required=5.0 tests=AWL,BAYES_00 X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of vdichev@gmail.com designates 209.85.219.209 as permitted sender) Received: from [209.85.219.209] (HELO mail-ew0-f209.google.com) (209.85.219.209) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 24 Oct 2009 20:26:47 +0000 Received: by ewy5 with SMTP id 5so6935974ewy.12 for ; Sat, 24 Oct 2009 13:26:26 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:received:in-reply-to :references:date:x-google-sender-auth:message-id:subject:from:to :content-type; bh=9KDkpvGNMDrORyPHzl+A3m/268cfGZ3xfPsnZDWKZP4=; b=KyOuMZ7XKjzYUm26Wb1yi4+BA6/Q8nf5Yz03EknJiVHG8zZ0RJrWwFQ//T/s++Ns9Y Hm/1+Uci0jMQm2eR+s06Oas8qWBlGEhEzZdbAPBaQ05KuMibxA968NwNG71cfvfW9SZi KVFFWeQAytOCuwgPwyqkBoU/FMcxVNLPO87iQ= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type; b=ELeBm++v7G7kr79VJgTSCSdqidO5hRvFRAFnEmgsVoX442tyPxurvKTx59xVoD6aJa vENk3YMS9SI++Lf+nMRrhuwX+6izX0h6+hf2fkcEax6vROiaBDmyLlJifcLbkljFvr9X OYw+uyuv1CSxW1Kd75MTIU6Pg9/blMlPdLaZs= MIME-Version: 1.0 Sender: vdichev@gmail.com Received: by 10.216.86.7 with SMTP id v7mr708038wee.203.1256415986407; Sat, 24 Oct 2009 13:26:26 -0700 (PDT) In-Reply-To: <8d32b3490910240128n3f6235f3p29d3abcdef4b72cd@mail.gmail.com> References: <8d32b3490910240128n3f6235f3p29d3abcdef4b72cd@mail.gmail.com> Date: Sat, 24 Oct 2009 23:26:26 +0300 X-Google-Sender-Auth: 2634107ed21ef211 Message-ID: Subject: Re: Code formatting / beautifier for Scala From: Vassil Dichev To: esme-dev@incubator.apache.org Content-Type: text/plain; charset=ISO-8859-1 > I don't have any ideas for a beautifier but I think coming up with coding > standards would be a good idea. I noticed going through the code that in one > place "user" might represent an instance of the User class and other times > it might represent a Long user id. Without declarative static typing of Java > it can be confusing figuring out which is which. Just an idea. We can use some naming convention, e.g. append "Id". But most IDEs can infer the type and show it (say, in a tooltip), right? Regarding code formatting, we must first agree on the formatting rules before applying some automatic code formatter. I'm not very happy with some automatic formatting, for instance deep indents for multiple nested method invocations tends to make line width very large quickly. Besides, I'm not sure at this point how detailed we want the formatting instructions to be.