News for hackers. Stuff that matters.
Re:How to convince any C developer to dump gcc and use clang by pgbovine on Sunday March 07, 2010 @02:21AM (#1173029)
just because the ui is more user-friendly?

Those better warnings aren't just due to a simple UI patch ... clang is doing better and deeper static analysis than gcc in order to even be able to produce those more intelligent warnings.

Re:How to convince any C developer to dump gcc and use clang by ahn on Sunday March 07, 2010 @04:28AM (#1173132)
gcc with the dehydra plugin is doing better and deeper static analysis than clang.
Re:How to convince any C developer to dump gcc and use clang by Zev on Sunday March 07, 2010 @08:28PM (#1174426)
Doesn't dehydra do static analysis for C++ code? In which case, of course it would do better then clang; clang doesn't even claim to have complete c++ support yet.
Re:How to convince any C developer to dump gcc and use clang by ssp on Sunday March 07, 2010 @06:17AM (#1173216)
There is nothing deep about these warnings. It would likely be really, really simple to add them to gcc.
Re:How to convince any C developer to dump gcc and use clang by orborde on Sunday March 07, 2010 @06:38AM (#1173235)
And yet, gcc doesn't have them.
Re:How to convince any C developer to dump gcc and use clang by ssp on Sunday March 07, 2010 @09:17PM (#1174486)
If you think these warnings are evidence that "clang is doing better and deeper static analysis than gcc", then you have no idea how compilers work.