[prev in list] [next in list] [prev in thread] [next in thread]
List: kde-frameworks-devel
Subject: Re: Banning QNetworkAccessManager
From: Nicolás_Alvarez <nicolas.alvarez () gmail ! com>
Date: 2020-02-20 15:57:46
Message-ID: CANPC-tv-qKFANzu7Dk4HRUqsFAYu6Gtf+DpC4p36nnAEu+Fe-Q () mail ! gmail ! com
[Download RAW message or body]
El jue., 20 de feb. de 2020 a la(s) 10:30, Allen Winter
(winter@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
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic