News for hackers. Stuff that matters.
Re:Measuring C API Coverage with Go by jessevdk on Wednesday December 04, 2013 @12:04PM (#6848271)
Shameless plug (but possibly interesting), we do something similar (but using clang) to generate a coverage report for the gobject bindings for libgit2: https://git.gnome.org/browse/libgit2-glib/tree/tools/coverag...
Re:Measuring C API Coverage with Go by SloopJon on Wednesday December 04, 2013 @12:29PM (#6848470)
Wow. Although I was vaguely aware that Clang is tool friendly, I had no idea about libclang, let alone its Python bindings. A search for "python clang module" turned up a mention of pycparser. Any idea how it compares? I guess its main advantage is that it's pure Python.
Re:Measuring C API Coverage with Go by ihnorton on Wednesday December 04, 2013 @02:21PM (#6849387)
Great introduction to libclang and cindex from Eli Bendersky:

http://eli.thegreenplace.net/2011/07/03/parsing-c-in-python-....

(another shameless plug: libclang bindings are also available for Julia)

Re:Measuring C API Coverage with Go by jessevdk on Wednesday December 04, 2013 @12:42PM (#6848589)
I can't really compare, because I've personally never used pycparser. The nice thing about using libclang is that you're just using the same backend as the actual compiler and you can be sure that you're going to parse complex things correctly and reliably.