<p dir="ltr">I only made the point (among a bunch of other points!) because I wondered if it was worth presenting consistency in D code intended for public scrutiny. It's all good, it's settled now. It's not my fault, or my intent, that the most trivial point in my list of comments is the one that apparently stimulated the most discussion... :/</p>
<div class="gmail_quote">On 14 Dec 2013 14:00, <"Ola Fosheim Grøstad\" &<a href="mailto:lt%3Bola.fosheim.grostad%2Bdlang@gmail.com">lt;ola.fosheim.grostad+dlang@gmail.com</a>&<a href="mailto:gt%3B%26quot%3B@puremagic.com">gt;"@puremagic.com</a>> wrote:<br type="attribution">
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Mmm, I prefer C braces for this reason.<br>
</blockquote>
<br>
There is no such thing as "C-braces" or idiomatic C. C is defined<br>
by anarchy and chaos. The reason old C-code (and guides) have<br>
braces on the next line for function calls is that the type was<br>
specified under the parameter-list in old-style C.<br>
<br>
<a href="http://en.wikipedia.org/wiki/Indent_style" target="_blank">http://en.wikipedia.org/wiki/<u></u>Indent_style</a><br>
<br>
Fixed rules for whitespace leads to poor legibility, creating legible<br>
layout is a context sensitive design problem.<br>
<br>
No wonder the D-language is stuck in a state of poor usability<br>
with discussions like this eating all the bandwidth…<br>
<br>
And, why, why, why would anyone think that it is a good idea to<br>
use the boolean negate-operator for templates? Talk about making<br>
my eyes sore! D has a large heap of usability and inconsistency<br>
problems that makes freedom-of-whitespace a drop in a biiiig<br>
ocean. Get real, you need to focus on real challenges if you want<br>
D to take off!<br>
<br>
(back to lurking)<br>
</blockquote></div>