Re: Code formatting / beautifier for Scala

[Richard Hirsch <hi...@gmail.com>]

Tried to install intelliJ and the tool doesn't work on my machine :-<

http://bit.ly/2YeihN

Someone else is going to have format the Scala files.

D.

On Sat, Oct 24, 2009 at 9:26 PM, Vassil Dichev <vd...@apache.org> wrote:
>> 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.
>

Re: Code formatting / beautifier for Scala

[Anne Kathrine Petterøe <ak...@gmail.com>]

If we can come up with coding standards, I'd be happy to help with the  
formatting.

/Anne

On 2. nov. 2009, at 15.41, Richard Hirsch wrote:

> Tried to install intelliJ and the tool doesn't work on my machine :-<
>
> http://bit.ly/2YeihN
>
> Someone else is going to have format the Scala files.
>
> D.
>
> On Sat, Oct 24, 2009 at 9:26 PM, Vassil Dichev <vd...@apache.org>  
> wrote:
>>> 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.
>>