[Python-Dev] Running Clang 2.7's static analyzer over the code base (original) (raw)
Victor Stinner victor.stinner at haypocalc.com
Wed May 5 23:01:50 CEST 2010
- Previous message: [Python-Dev] Running Clang 2.7's static analyzer over the code base
- Next message: [Python-Dev] Running Clang 2.7's static analyzer over the code base
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Le mardi 04 mai 2010 00:37:22, Brett Cannon a écrit :
Since 2.7 is probably going to exist for a while, I am running Clang 2.7's static analyzer (
clang --static) over trunk. It's mostly just finding stuff like unneeded variable initialization or variables that are never used (compilation is picking up unused returned values, almost all from PyObjectINIT).When I check in these changes I will do it file by file, ...
Do you plan to port the changes to py3k? and what about 2.6 and 3.1?
--
Please don't change whitespaces in the same commit. I think that we should fix the whitespaces of the whole project in one unique commit. Well, or least don't fix whitespaces file by file...
-- Victor Stinner http://www.haypocalc.com/
- Previous message: [Python-Dev] Running Clang 2.7's static analyzer over the code base
- Next message: [Python-Dev] Running Clang 2.7's static analyzer over the code base
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]