|
| 1 | +<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN" "http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd"> |
| 2 | +<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en"> |
| 3 | +<head> |
| 4 | + <meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /> |
| 5 | + <meta name="description" content="google summer of code 2014 ideas" /> |
| 6 | + <meta name="keywords" content="Cppcheck, google summer of code" /> |
| 7 | + <title>google summer of code 2014 ideas</title> |
| 8 | + <link rel="stylesheet" type="text/css" href="//fonts.googleapis.com/css?family=Orbitron&text=Cppcheck" /> |
| 9 | + <link rel="stylesheet" type="text/css" href="/site/css/pack.css" /> |
| 10 | + <link rel="shortcut icon" type="image/x-icon" href="/favicon.ico" /> |
| 11 | +</head> |
| 12 | +<body> |
| 13 | +<div id="header"> |
| 14 | + <div class="wrap"> |
| 15 | + <h1><a href="/">Cppcheck</a></h1> |
| 16 | + <p>A tool for static C/C++ code analysis</p> |
| 17 | + </div> <!-- .wrap --> |
| 18 | +</div> <!-- #header --> |
| 19 | +<div id="tabs"> |
| 20 | + <div class="wrap"> |
| 21 | + <ul> |
| 22 | + <li><a href="/">Home</a></li> |
| 23 | + <li><a href="http://sourceforge.net/apps/mediawiki/cppcheck/">Wiki</a></li> |
| 24 | + <li><a href="http://sourceforge.net/apps/phpbb/cppcheck/">Forum</a></li> |
| 25 | + <li><a href="http://sourceforge.net/apps/trac/cppcheck/">Issues</a></li> |
| 26 | + <li><a href="/devinfo/" title="Developer Information">Developer Info</a></li> |
| 27 | + <li><a href="/demo/">Online Demo</a></li> |
| 28 | + <li><a href="http://sourceforge.net/projects/cppcheck/">Project page</a></li> |
| 29 | + </ul> |
| 30 | + </div> <!-- .wrap --> |
| 31 | +</div> <!-- #tabs --> |
| 32 | +<div id="content"> |
| 33 | + <div class="wrap"> |
| 34 | +
|
| 35 | + <h2>Overview</h2> |
| 36 | +
|
| 37 | + <p> |
| 38 | + <ol> |
| 39 | + <li>Core Cppcheck |
| 40 | + <ol> |
| 41 | + <li>Add a new checker (C++)</li> |
| 42 | + <li>Improved value flow (C++)</li> |
| 43 | + </ol></li> |
| 44 | + <li>Configurations |
| 45 | + <ol> |
| 46 | + <li>Write more configurations (XML)</li> |
| 47 | + <li>Auto generate configuration (C++ / scripting) |
| 48 | + <li>GUI for editing configurations (C++,Qt)</li> |
| 49 | + </ol></li> |
| 50 | + <li>Distributed computing |
| 51 | + <ol> |
| 52 | + <li>Distributed computing (C++)</li> |
| 53 | + </ol></li> |
| 54 | + </ul> |
| 55 | + </p> |
| 56 | +
|
| 57 | + <h2>1. Core Cppcheck</h2> |
| 58 | +
|
| 59 | + <p> |
| 60 | + <strong>Project 1.1</strong><br> |
| 61 | + <strong>Name:</strong> Add a new checker<br> |
| 62 | + <strong>Skills required:</strong> C++<br> |
| 63 | + <strong>Description:</strong> There are several tickets in our issue tracker that has ideas for new checkers. |
| 64 | + The subtasks will be: implement a new checker, write test cases, test it against various projects. |
| 65 | + </p> |
| 66 | +
|
| 67 | + <p> |
| 68 | + <strong>Project 1.2</strong><br> |
| 69 | + <strong>Name:</strong> Improved value flow<br> |
| 70 | + <strong>Skills required:</strong> C++<br> |
| 71 | + <strong>Description:</strong> The value flow analysis is used by various checkers - therefore improving |
| 72 | + this will mean that many checkers get better. It is possible to improve the value flow analysis, for example |
| 73 | + after conditions, inside loops, etc. |
| 74 | + </p> |
| 75 | +
|
| 76 | +
|
| 77 | + <h2>2. Configurations</h2> |
| 78 | +
|
| 79 | + <p> |
| 80 | + <strong>Project 2.1</strong><br> |
| 81 | + <strong>Name:</strong> Write more configurations<br> |
| 82 | + <strong>Skills required:</strong> XML<br> |
| 83 | + <strong>Description:</strong> More configuration files are needed for various libraries. It |
| 84 | + would be most interesting to have more configurations for popular libraries. |
| 85 | + </p> |
| 86 | +
|
| 87 | + <p> |
| 88 | + <strong>Project 2.2</strong><br> |
| 89 | + <strong>Name:</strong> Autogenerated configurations<br> |
| 90 | + <strong>Skills required:</strong> C++ / scripting<br> |
| 91 | + <strong>Description:</strong> Auto generate configuration from headers. To parse the headers, |
| 92 | + you can for instance do this yourself (python script/c++/..) or you can modify cppcheck and |
| 93 | + use the symboldatabase. |
| 94 | + </p> |
| 95 | +
|
| 96 | + <p> |
| 97 | + <strong>Project 2.3</strong><br> |
| 98 | + <strong>Name:</strong> GUI for editing configurations<br> |
| 99 | + <strong>Skills required:</strong> C++, Qt<br> |
| 100 | + <strong>Description:</strong> A graphical user interface for editing configurations would be nice. This should be |
| 101 | + added in the cppcheck-gui program. |
| 102 | + </p> |
| 103 | +
|
| 104 | + <h2>3. Distributed computing</h2> |
| 105 | +
|
| 106 | + <p> |
| 107 | + <strong>Project 3.1</strong><br> |
| 108 | + <strong>Name:</strong> Distributed computing<br> |
| 109 | + <strong>Skills required:</strong> Network, script, C++<br> |
| 110 | + <strong>Description:</strong> Make it possible to distribute analysis. A client and server needs to be written. The client will |
| 111 | + execute cppcheck to perform analysis. |
| 112 | + </p> |
| 113 | +
|
| 114 | + </div> <!-- .wrap --> |
| 115 | +</div> <!-- #content --> |
| 116 | +
|
| 117 | +</body> |
| 118 | +</html> |
0 commit comments