> Hum... I just had a thought. What if the output was reformatted as an html > table? One row per library with columns for the error counts for the > different kinds of errors. Click through to see the actual error messages. > > That would give us an overview we could watch as we approached releases. > > Anyone like to volunteer to write such a program? It should probably be > separate from inspect itself to separate the concern of detecting errors > separate from reporting concerns. > > Thoughts? > > --Beman
Meanwhile I updated xenu broken links report here: http://groups.yahoo.com/group/boost/files/BrokenLinksReport.html Looks useful. It does not provide a statistics though. Gennadiy. P.S. I have a feeling that it gives false alarms simetimes (rarely). Don't blame me. _______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
