|
From: Josef W. <Jos...@gm...> - 2007-08-28 23:40:00
|
On Wednesday 29 August 2007, Benjamin Meyer wrote: > What was confusing me was that I figured it would write "0" rather > then "-84" (because 0 is only one char vs three and more likely to > occur, leading to better compression) Yeah, missed space optimization in the dump file writing. Should be easy to change. > This class replaces the valgrind tool I wrote last week to acquire > coverage data. It is a much cleaner solution. Once it has the > information it is combined with the ast tree for the source I want to > get coverage on and it then generates a report. Below is the first > version of this report: > [...] Cool. Where to you have the AST from? > Lines not touched: > 167 [c] c: ulong self; I assume there is not really code for this line... Otherwise, it looks really promising! Josef |