On 13-09-30 13:46, Stefan Schmidt wrote: > Hello. > > *** Newsflash *** > New research paper unvails that looking at potential problems early in > the development and release process cuts down time spent on debugging > aftterwards. Suggestions have been made that developers should have a > look at these potential problems and either fix them or mark as incorrect. > ***
I do agree with that statement. > Coverity: > o EFL: Outstanding defects 455 (449) with a density of 0.86 (0.85). 2 > defects fixed since last build and 8 added. > o Elm: Outstanding defects 22 (21) with a density of 0.10 (0.09). 0 > defects fixed since last build and 1 added. > o E: Outstanding defects 202 (198) with a density of 0.72 (0.71). 0 > defects fixed since last build and 4 added. Could you test terminology? I won't be able to look into such reports before long, maybe not even before the EFL dev day but I'd like to have them in the near future. Thank you for your work. -- Boris Faure Pointer Arithmetician ------------------------------------------------------------------------------ October Webinars: Code for Performance Free Intel webinars can help you accelerate application performance. Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from the latest Intel processors and coprocessors. See abstracts and register > http://pubads.g.doubleclick.net/gampad/clk?id=60133471&iu=/4140/ostg.clktrk _______________________________________________ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
