A RetroSearch Logo

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Search Query:

Showing content from https://mail.python.org/pipermail/python-dev/2010-May/099925.html below:

[Python-Dev] Running Clang 2.7's static analyzer over the code base

[Python-Dev] Running Clang 2.7's static analyzer over the code base [Python-Dev] Running Clang 2.7's static analyzer over the code baseVictor Stinner victor.stinner at haypocalc.com
Tue May 4 10:14:19 CEST 2010
Le mardi 04 mai 2010 01:24:37, Antoine Pitrou a écrit :
> Would it be finally time to standardize all C files on a 4-spaces
> indentation rule?

Indentation is painful on some files mixing tabs and spaces (sometimes in the 
same function!).

> I understand the "svn annotate" argument, but we edit code far more often
> than we annotate it. Also, it seems "svn ann -x -w" would ignore
> whitespace changes.

I use svn blame to find the commit which insered a line of code. When I get 
the commit number, I always read the commit to ensure that the patch really 
insered the line, and it's not a refactoring patch. Refactoring can be about 
the indentation, but there are a lot of other minor changes: op->ob_size => 
Py_SIZE(op), (a) => a, { with a new line => { without newline, ...

-- 
Victor Stinner
http://www.haypocalc.com/
More information about the Python-Dev mailing list

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4