Clang-Based Tool Makes It Easy To Show Inefficient Qt Coding Mistakes

[phoronix]

Phoronix: Clang-Based Tool Makes It Easy To Show Inefficient Qt Coding Mistakes

Back in 2017 we wrote about the "Clazy" static analyzer for Clang as a way to uncover various coding shortcomings for KDE/Qt programs. Since then, Clazy has become much more capable...

http://www.phoronix.com/scan.php?page=news_item&px=Clang-Clazy-Qt-Slow-Mistakes

[chuckula]

IN B4 APOSTROPHE GUY!!

"Back in 2017 we wrote about the "Clazy" static analyzer for Clang"

Think about the "2017" for a second.
Then replace with "2015".

[Michael]

IN B4 APOSTROPHE GUY!!

"Back in 2017 we wrote about the "Clazy" static analyzer for Clang"

Think about the "2017" for a second.
Then replace with "2015".

Heh thanks, fixed.

[uid313]

Hope to see this for GTK too.

[tildearrow]

I never catch number typos. Though I was kind of confused after reading "2017".

Also, why is GCC unsuitable for this kind of projects? Why Clang? (If it causes havoc, I'm sorry)

[cj.wijtmans]

I never catch number typos. Though I was kind of confused after reading "2017".

Also, why is GCC unsuitable for this kind of projects? Why Clang? (If it causes havoc, I'm sorry)

i was wonderin the same thing why cant it be done with gcc. GCC doesnt have the infra probably?

[geearf]

I never catch number typos. Though I was kind of confused after reading "2017".

Also, why is GCC unsuitable for this kind of projects? Why Clang? (If it causes havoc, I'm sorry)

I usually read that clang outputs better information to help coding/debugging. That might have been years ago though.

[starshipeleven]

I usually read that clang outputs better information to help coding/debugging. That might have been years ago though.

Afaik this was improved years ago.

[mmstick]

I never catch number typos. Though I was kind of confused after reading "2017".

Also, why is GCC unsuitable for this kind of projects? Why Clang? (If it causes havoc, I'm sorry)

LLVM compiler plugins are a huge incentive for language tool authors to use LLVM. GCC has always been hostile towards compiler plugins due to fears over the possibility of proprietary compiler plugins.

[tessio]

LLVM compiler plugins are a huge incentive for language tool authors to use LLVM. GCC has always been hostile towards compiler plugins due to fears over the possibility of proprietary compiler plugins.

https://lwn.net/Articles/629259/

GNU is to blame for making GCC less relevant.. The fear of proprietary software consumed Stallman and turned him to the dark side.