Malcolm Purvis <malcolmpurvis(a)optushome.com.au> wrote:
Which reminds me, Jerry is that scanning tool you were working on
ready for general use yet?
It's Uno: http://spinroot.com/uno/
It is in significantly better shape now that when I first started trying
to use it last summer. Holzmann fixed quite a list of bugs I reported
to him, and was gracious enough to include some code I sent him that
enables use of Uno on code bases with more than one directory. It still
isn't perfect, but it's a lot better. The major weakness now is that
the tool doesn't track function pointers very well, so lots of the code
never gets traced, because it is only ever called through function
pointers. Also, since Uno doesn't know about callbacks, this also means
that gobs of the redisplay code is never touched.
I need to start writing XEmacs-specific Uno tests, but I've been in "I'm
too busy to breathe" mode for the last few months. That should settle
down soon, but I've probably got a couple of weeks of insanity left.