A look at the D programming language by Ferdynand Górski

[Chris]

> class:
>     def:
>         for:
>             if:
>
> You could call it "south west" code.
>

Recte: South east code, of course!

> Then I started working in multi-site projects with developers 
> from all types of backgrounds, and understood the value of a 
> consistent project code formatting.
>
> --
> Paulo

In most languages, there are coding conventions, and projects 
should have consistent formatting. I agree. However, I think 
indentation as part of the syntax is highly exaggerated. A 
language can and should protect programmers from making stupid or 
common mistakes and offer features that make programming more 
efficient and software more reliable. To enforce a certain 
aesthetic style, based on personal preferences more often than 
not, should not be part of the language, but up to the teams that 
use the language. On top of that, Python code can be messy too 
(although it might look "nice"). In _my_ experience, readability 
is often impeded by the use of obscure variable and function 
names.

v = r.calc(m.get_p() / m.get_r())

What is "v", what is calc() calculating ...?

Such code can be due to laziness or arrogance. But no language 
feature can prevent bad or lazy programmers from producing such 
code, even if it's nicely formatted.

Anyway, 1,000 programmers will have 1,001 views on coding style.