<br><br>
<div class="gmail_quote">On Feb 17, 2008 3:19 AM, Matti Bickel <<a href="mailto:cat5@minet.uni-jena.de">cat5@minet.uni-jena.de</a>> wrote:<br>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid"><br>I'm really in favour of adopting a more liberal space usage. While i'll<br>not go after anyone if that's rejected, i think it's more in line with<br>
the general generous use of whitespace in the code anyway...<br></blockquote>
<div>I agree 100% with respect to whitespace.</div>
<div>whitespace after commas and around operators is much more readable in my oppinion.</div>
<div> </div>
<div>I woud also favor K&R style curly bracket placement, but that's a little less important to me than the whitespace.</div>
<div> </div>
<div> </div>
<div>I don't think anyone is going to re-format everything at once, so this is what I would keep in mind as I'm working on TORQUE:</div>
<div> </div>
<div>in order of importance:</div>
<div> </div>
<div>#1 - consistency within a function</div>
<div> </div>
<div>#2 - consistency within an entire source file</div>
<div> </div>
<div>#3 - consistency between relaited source files</div>
<div> </div>
<div>#4 - consistency between all source files</div>
<div> </div>
<div> </div>
<div> </div>
<div>and I preffer a pretty short and consise set of coding GUIDELINEs rather than a long, complicated, and rigid STANDARD</div></div>