Difference between revisions of "Other Tools"
From Apache OpenOffice Wiki
| (3 intermediate revisions by the same user not shown) | |||
| Line 35: | Line 35: | ||
*[http://delta.tigris.org/ delta], for delta-debugging input data | *[http://delta.tigris.org/ delta], for delta-debugging input data | ||
| − | *[[testshl2]] | + | *[[testshl2]], OOo's own version of c++ unit tests |
| + | *[http://fitnesse.org/ FitNesse], bunch of tools for test-driven development | ||
| + | |||
| + | |||
| + | ==X11-specific== | ||
| + | |||
| + | *[http://projects.o-hand.com/xephyr xephyr] nested X server with <em>all</em> contemporary extensions | ||
| + | *[http://projects.o-hand.com/xrestop xrestop] X resource profiling (parse it x res top) | ||
| + | *[http://projects.o-hand.com/xresponse xresponse] X client for measuring response timing | ||
Latest revision as of 09:26, 4 October 2006
This page is a bag of misc: links to a ton of tools people might find useful, for grokking, analysing, testing, and transforming OOo's code base
Static code analysis
- Wikipedia
- SPIN model checker
- Inspector
- OpenC++
- why this is hard for c++
- SourceNav
- Harmonia
- Oink Data flow analysis
Front ends
Flawfinder and similar
- AntiC
- FlawFinder
- Rough_Auditing
- cpd Copy'n'Paste detector
Code Metrics
Testing
- delta, for delta-debugging input data
- testshl2, OOo's own version of c++ unit tests
- FitNesse, bunch of tools for test-driven development
X11-specific
- xephyr nested X server with all contemporary extensions
- xrestop X resource profiling (parse it x res top)
- xresponse X client for measuring response timing
C++ Parsing
- Why c++ parsing is hard: http://www.nobugs.org/developer/parsingcpp/mikedimmick.txt
- several links to C++ parsers/frontends: http://os.inf.tu-dresden.de/vfiasco/related.html
- gcc's tree dumping options: http://gcc.gnu.org/onlinedocs/gcc/Debugging-Options.html#Debugging-Options
