On 9/28/06, Ralph Schindler <[EMAIL PROTECTED]> wrote:
Matthew Weier O'Phinney wrote:
> -- P?draic Brady <[EMAIL PROTECTED]> wrote
> (on Thursday, 28 September 2006, 01:24 AM -0700):
>> Parts of the standards seem to follow opposing preferences. While
>> functions and methods place the opening brace on its own line, control
>> statements state they should place on the same line as the statement
>> def.
>>
>> Seems a bit odd. I usually do the opposite :), but esp. not placing
>> control statement braces on a new line reduces readability IMO. A
>> method def is easy to spot - following control statements is far more
>> complicated.
>
> Odd as it may seem, it's a fairly well-known standard often referred to
> as the 'One True Brace':
>
> http://wikipedia.org/wiki/One_true_brace
>
> The style is also used in PEAR and Linux kernel development.
>
And those are conventions I would expect from those projects... they are
stuck in an age where blacks drank from one water fountain, whites from
another, and developers had 6 line screen terminal.
But since those times, we as developers have pressed on. We have gotten
bigger screens running IDE's with code folding and since have started to
condemn this BRACISM. We have since started offering equal opportunity
to all braces, allowing any brace to drink from the proverbial water
fountain. All braces should live in harmony of their own line.
I understand that you cant teach old dogs new tricks, and in that
respect, we should make this "One True Brace" rule optional. Let the
brace haters have their way, for they will die soon of old age or simply
the explosion of hate that lives within.
Join me in celebrating a world without bracism.
http://www.urbandictionary.com/define.php?term=bracism
Braces: Separate but equal, End Bracism Now!
;)
--
best regards,
André Hoffmann
ZF-Blog: http://andrehoffmann.wordpress.com/
