Web lists-archives.com

Re: auto QString(Builder) considered VERY HARMFUL -> use clazy /w kdevelop

Darn, forgot some obvious promo bits... see below:

Am Donnerstag, 27. September 2018, 21:01:13 CEST schrieb Friedrich W. H. 
> Am Donnerstag, 27. September 2018, 20:08:54 CEST schrieb Andreas Hartmetz:
> > Please take care.
> Care can be done e.g. by deploying clazy with
> auto-unexpected-qstringbuilder:
> clazy-standalone \
> 	-checks=auto-unexpected-qstringbuilder  -p <buildroot>  <projectroot>
> See
> https://phabricator.kde.org/source/clazy/browse/master/docs/checks/README-au
> to-unexpected-qstringbuilder.md?as=remarkup
> https://phabricator.kde.org/source/clazy/browse/master/README.md?as=remarku
> p
> One would recommend to run clazy over your code at least before releases, to
> catch all kind of potential issues :)

If you are using KDevelop, upcoming version 5.3 features clazy integration.

So it is just a matter of selecting "auto-unexpected-qstringbuilder" in the 
config UI, and then triggering a run of Clazy over the whole project, some 
subdir or just a single source file :)

Test yourself by getting a Nightly Build of what very soon is becoming 
KDevelop 5.3 from here: https://www.kdevelop.org/download

Needs a separate clazy installation. Well stuffed distribution repos should 
provide packages for you (like for Arch Linux, openSUSE Tumbleweed or 
Building clazy yourself works as well, just needs careful reading of 
instructions about clazy-standalone binary location in the README.md file. And 
building with just -j 1, compiling against clang/llvm makes the compiler eat 
lots of your memory :)