View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0003175 | DarkRadiant | Design/Coding | public | 09.07.2012 14:51 | 25.06.2016 13:06 |
Reporter | lbalbalba | Assigned To | |||
Priority | normal | Severity | normal | Reproducibility | always |
Status | closed | Resolution | won't fix | ||
Platform | Linux | ||||
Product Version | 1.7.0 | ||||
Summary | 0003175: static src analysis for fun and profit | ||||
Description | I have been playing around with the llvm/clang static source code analyzer (http://clang.llvm.org/get_started.html) for a while, and thought it might be fun to run it on the darkradiant source code. For those interested the results might can be found here : http://lbalbalba.x90x.net/clang-analyzer/darkradiant/ Please note that the clang C++ compiler also found some compilation errors (at the bottom of the page), that GCC shouldnt even accept in the 1st place, like this one : 'boost::python::object' can actually refer to two different things, either namespace boost { namespace python { class object; } } or namespace boost { namespace python { namespace api { class object; } using api::object } } | ||||
Tags | No tags attached. | ||||
Thanks. :) | |
No problem. Just wondering: Did you get a chance to take a look at the report yet ? Or are they all just 'false positives' ? :( | |
Updated the report to clang version 3.3 (trunk 171337) | |
Link is dead in the meantime, and the code has changed a lot since then, closing for now. | |
Date Modified | Username | Field | Change |
---|---|---|---|
09.07.2012 14:51 | lbalbalba | New Issue | |
17.07.2012 14:14 | greebo | Note Added: 0004714 | |
17.07.2012 14:14 | greebo | Status | new => acknowledged |
05.08.2012 11:25 | lbalbalba | Note Added: 0004737 | |
02.01.2013 13:32 | lbalbalba | Note Added: 0004982 | |
25.06.2016 13:06 | greebo | Note Added: 0008220 | |
25.06.2016 13:06 | greebo | Status | acknowledged => closed |
25.06.2016 13:06 | greebo | Resolution | open => won't fix |