brackets

And that the sum of parens+brackets+braces is similar to other languages, just the distribution is different.

However, in the surrounding countries from the Eurozone, tax rates for similar income brackets tend to be significantly higher.

Don't bother in this case, the brackets are usual notation for the floor function.

Devising new ways to litter code with <> brackets smells suspiciously like C++.

A little confusing because ruby doesn't require brackets for zero argument function calls.

A better rule is that hard-to-rememeber precedence rules should require brackets.

Change brackets to dashes (like this) - or like this.

And then there are the curly braces and mandatory brackets for function calls, but I think that can't be what everybody hates (Ruby is more verbose with do end instead of brackets, isn't it?).

In the United States though, that is the largest tax deduction available to John/Jane Doe and a significant incentive to buy a house in some tax brackets.

But it doesn't have brackets and semicolons.

It looks like US and CA income tax has brackets, so even if your marginal rate is 37% you won't be paying that rate on 100% of your income.

I can never remember those if I need to do a `x * y + 2 z --` and so always write in brackets explicitly.

Notice how they put "also known as double opt-in" in brackets, and then never use it again but only use confirmed opt-in?

The case is obvious for the poor, but as you go to higher income brackets more and more of the possibilities fall into "luxury" and "status symbol".

This has been my attitude so far, and my original title (before being edited) had "[How]" in brackets: I'm not at all sure what to do.

> as you go to higher income brackets more and more of the possibilities fall into "luxury" and "status symbol".