Banning QNetworkAccessManager

Nicolás Alvarez nicolas.alvarez at gmail.com
Thu Feb 20 15:57:46 GMT 2020


El jue., 20 de feb. de 2020 a la(s) 10:30, Allen Winter
(winter at kde.org) escribió:
>
> On Wednesday, February 19, 2020 6:09:02 PM EST Albert Astals Cid wrote:
> > El dimecres, 19 de febrer de 2020, a les 9:28:22 CET, Volker Krause va escriure:
> > > Additionally, improved documentation, a possible KNAM and/or driving the QNAM
> > > changes upstream can still be done alongside this obviously.
> >
> > Also for Qt5 which will probably never be changed a clazy warning and making it easy to run clazy on gitlab CI would be great.
> >
>
> Krazy has a checker for QNetworkAccessManager use in Qt4 code.
> I could add a checker for Qt5 code if someone tells me what to look for
> (not that many people look at krazy reports. couldn't hurt. might help.

I started making a checker for this based on clang-static-analyzer.
Looks like clazy uses a different approach altogether by looking at
ASTs alone, so I don't think I can integrate into that...

-- 
Nicolás


More information about the Kde-frameworks-devel mailing list