On Fri, Jun 19, 2015 at 6:31 PM, Benjamin Fritz <[email protected]> wrote: > > On Fri, Jun 19, 2015 at 5:24 PM, Benjamin Fritz <[email protected]> > wrote: >> >> > Coverity should run automatically. I haven't checked the output >> > recently. There used to be quite a few false positives, maybe it's >> > better now. >> > >> > I'm not sure the Vim results are available to others or can be made >> > available. >> > >> >> According to https://scan.coverity.com/projects/241 Vim's last scan was in >> 2013. > > By the way, that scan had these results: > > vim: 302,420 line of code and 0.27 defect density > > "Defect Density" is measured in detected defects per 1000 lines of code. So > Vim has about 3 defects per 10,000 lines of code. > > Coverity says projects of similar size have about a 0.5 for defect density > on average. So we're in pretty good shape. :-) > > (Just for fun, https://scan.coverity.com/projects/2227 neovim/neovim: > 208,104 line of code and 0.43 defect density)
Just FYI, after the initial import from Vim 7.4.160, Neovim started with 138 defects in 180k LOC. At present, coverity reports 89 outstanding defects in 207k LOC. Neovim Coverity reports are generated three times per week. Ben (and anyone else) if you request access at https://scan.coverity.com/projects/2227 you'll be approved. And any bugs you fix will make it back to Vim :) Justin M. Keyes -- -- You received this message from the "vim_dev" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups "vim_dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
