[Python-Dev] Update PEP 7 to require curly braces in C (original) (raw)
Martin Panter vadmium+py at gmail.com
Tue Jan 19 22:33:37 EST 2016
- Previous message (by thread): [Python-Dev] Update PEP 7 to require curly braces in C
- Next message (by thread): [Python-Dev] Update PEP 7 to require curly braces in C
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On 19 January 2016 at 20:12, Brett Cannon <brett at python.org> wrote:
Here is a proposed update:
diff -r 633f51d10a67 pep-0007.txt --- a/pep-0007.txt Mon Jan 18 10:52:57 2016 -0800 +++ b/pep-0007.txt Tue Jan 19 12:11:44 2016 -0800 @@ -75,9 +75,9 @@ } * Code structure: one space between keywords like
if
,for
and - the following left paren; no spaces inside the paren; braces may be - omitted where C permits but when present, they should be formatted - as shown:: + the following left paren; no spaces inside the paren; braces are + strongly preferred but may be omitted where C permits, and they + should be formatted as shown:: if (mro != NULL) { ...
This change seems to be accidentally smuggled in, in the guise of a PEP 512 update :)
My view is I prefer always using curly brackets in my own code. It is easier to add printf() debugging without making mistakes. I support “strongly preferring” them in the style guide, which is as much as a style guide can do anyway.
- Previous message (by thread): [Python-Dev] Update PEP 7 to require curly braces in C
- Next message (by thread): [Python-Dev] Update PEP 7 to require curly braces in C
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]