proper use of braces in Python (was: Prothon Prototypes vs PythonClasses)

[Michael]

Right. Then we can have "does the brace go on the same line or the
next line" wars.

int main (void)
{
if (true)
{
}

return 0;
}

There is no other way.

No way, that wastes an entire line of code with a single brace!

int main ( void ) {
if ( true ) {
return 1;
}
return 0;
}

This is clearly better. Compact yet easy to read. I try formatting my
Python code exactly like this and it always complains about my braces..
clearly wrong.

[Peter Maas]

Michael wrote:

int main (void)
{
if (true)
{
}

return 0;
}

There is no other way.

No way, that wastes an entire line of code with a single brace!

Why not? It's a cheap way to increase your LOC/month power. :)

Mit freundlichen Gruessen,

Peter Maas

--
-------------------------------------------------------------------
Peter Maas, M+R Infosysteme, D-52070 Aachen, Hubert-Wienen-Str. 24
Tel [phone] Fax [phone] eMail pe********@mplusr.de
-------------------------------------------------------------------

[Michael]

Why not? It's a cheap way to increase your LOC/month power. :)

Good point, but that is why I like to make sure my code is well
documented. The more detailed the code is documented the higher the
LOC/month. :)

Actually, I do document rather well usually. I'm especially fond of
pydoc allowing a program to access it's own documentation. I love being
able to get the help for my XML-RPC methods just by formatting (as HTML)
the existing Python docs for those methods. Very tidy.

[Paul McGuire]

"Michael" <mo*****@mlug.missouri.edu> wrote in message
news:ma**************************************@pyth on.org...

Right. Then we can have "does the brace go on the same line or the
next line" wars.

int main (void)
{
if (true)
{
}

return 0;
}

There is no other way.

No way, that wastes an entire line of code with a single brace!

int main ( void ) {
if ( true ) {
return 1;
}
return 0;
}

This is clearly better. Compact yet easy to read. I try formatting my
Python code exactly like this and it always complains about my braces..
clearly wrong.

http://c2.com/cgi/wiki/wiki?WhereDoTheBracesGo

Not having to deal with this #$*^!!@ is just about my favorite feature of
Python! (Although I'm not excited about getting into a thread on an issue
that is so flame-prone. Honestly, though. "There is no other way."? "This
is clearly better."? I really interpret your stance as "This is the way I'm
used to." What's annoying is the added "... and therefore superior."
implication. The visual cues provided by brace placement are extremely
subjective, and what is "clearly better" to one is confusing to another.)

Is it so difficult to accept that this is a personal style/preference issue?
I agree that having a consistent form across an entire project makes things
simpler overall, it's not worth the aggravation of coercing a style on those
who vigorously and adamantly prefer their own. Furthermore,...

Oh wait, Python doesn't *have* braces! Whew! (What a funny subject for a
thread on c.l.py - April Fool's Day is come a bit early?)

-- Paul

[Carl Banks]

Paul McGuire wrote:

"Michael" <mo*****@mlug.missouri.edu> wrote in message
news:ma**************************************@pyth on.org...

>>Right. Then we can have "does the brace go on the same line or the
>>next line" wars.
>>
>>
>
> int main (void)
> {
> if (true)
> {
> }
>
> return 0;
> }
>
>There is no other way.
>
>

No way, that wastes an entire line of code with a single brace!

int main ( void ) {
if ( true ) {
return 1;
}
return 0;
}

This is clearly better. Compact yet easy to read. I try formatting my
Python code exactly like this and it always complains about my braces..
clearly wrong.

http://c2.com/cgi/wiki/wiki?WhereDoTheBracesGo

Not having to deal with this #$*^!!@ is just about my favorite feature of
Python! (Although I'm not excited about getting into a thread on an issue
that is so flame-prone. Honestly, though. "There is no other way."? "This
is clearly better."? I really interpret your stance as "This is the way I'm
used to." What's annoying is the added "... and therefore superior."
implication. The visual cues provided by brace placement are extremely
subjective, and what is "clearly better" to one is confusing to another.)

Paul,

What you're seeing here is a couple Pythonistas mocking C and Java
programmers who take these sorts of arguments dead-seriously. (But
not Perl programmers: they don't actually use braces. :)

Here at Python, we like to think that we argue about more important
things. It's part of the Zen of Python: there should only be one way
to do it. Because when there's more than one way to do it, you get
arguments like this.

"More than one way to do it" has led to the space vs. tab arguments we
have here. As far as I'm concerned, the biggest problem with spaces
and tabs is that you can use either, i.e., there's *unnecessarily*
more than one way to do it. And the Python Gods are rightly getting
rid of that.
--
CARL BANKS http://www.aerojockey.com/software
"If you believe in yourself, drink your school, stay on drugs, and
don't do milk, you can get work."
-- Parody of Mr. T from a Robert Smigel Cartoon