3 ms·
Cool, didn't notice they are doing C# as well. It would be very interesting to try it. I wonder what the costs are though - the quotes are hidden from their sit
by tener 10y ago
Cool, didn't notice they are doing C# as well. It would be very interesting to try it. I wonder what the costs are though - the quotes are hidden from their site.
Still, in reality, knowing that your code has a bug is just one part of the story. Having huge legacy code base usually means you've got to fix the bugs as you go about your business implementing features/fixing other bugs. You cannot simply spend a year fixing bugs no-one actually cares about (because software was working well enough before).
So in this drive-by scenario IDE-integrated tool is much more useful than some offline report-generating tool. You see a warning live in your editor - you fix the issue - you move on. Very low effort and effective in the long run.
- AndreyKarpov 10y ago> I wonder what the costs are though - the quotes are hidden from their site. You can easy try PVS-Studio. Explanation about the PVS-Studio demo-version limitations: http://www.viva64.com/en/b/0395/ http://www.viva64.com/en/b/0395/ > You cannot simply spend a year fixing bugs no-one actually cares about (because software was working well enough before). Yes. You can analysis only newly written code. Best Practices of using PVS-Studio. Now with C# support: http://www.viva64.com/en/b/0364/ http://www.viva64.com/en/b/0364/