From: serialhex <serialhex@...>
Date: 2011-09-13T05:39:36+09:00
Subject: Re: Any downsides to writing paranthesises?

On Mon, Sep 12, 2011 at 4:16 PM, Vladimir Van Bauenhoffer
<cluny_gisslaren@hotmail.com> wrote:
>
> Im a newbie programmer who is trying to learn Ruby after having just
> learned the basics of Python. Being used to Python I very much like
> having paranthesises when I code because for me it is easier to read and
> I also think it looks more structured.
>
> I know that Ruby encourages you to not use paranthesises in most cases,
> but my question is: are there any downsides to using paranthesises? I
> dont know much about programming and I would very much like to know if
> there is a problem with me using paranthesises pretty much everywhere in
> Ruby.
>
> --
> Posted via http://www.ruby-forum.com/.
>

while there isn't anything implicitly *wrong* with using parens all
over the place, IMO (and in most ruby-ists opinion probably) an
overabundance of parens looks ugly.  case in point:

```
"foo".to_a().length()
# vs
"foo".to_a.length
```

the first, with the un-needed parens is kind of ugly, the second, not
so much.  (in fact, the fact that i *must* include the parens with
functions that take no arguments infuriates me to no end!  it's like
ending every line with a freaking semicolon!!! OOHHHH!!!! STAB
PEOPLE!!!!!!)

but in the end, it's your code, do what you will
hex


--
*  my blog is cooler than yours: http://serialhex.github.com
*  The wise man said: "Never argue with an idiot. They bring you down
to their level and beat you with experience."
*  As a programmer, it is your job to put yourself out of business.
What you do today can be automated tomorrow. ~Doug McIlroy