https://bugs.kde.org/show_bug.cgi?id=353767
Sergio Martins changed:
What|Removed |Added
Resolution|--- |FIXED
Status|CONFIRMED
https://bugs.kde.org/show_bug.cgi?id=353767
Sergio Martins changed:
What|Removed |Added
Assignee|unassigned-b...@kde.org |smart...@kde.org
--
You are receiving this ma
https://bugs.kde.org/show_bug.cgi?id=353767
--- Comment #5 from Sergio Martins ---
Git commit 4aa04494e33dcf5e853d76bacec2afb58a7e0100 by Sergio Martins.
Committed on 24/04/2016 at 12:40.
Pushed by smartins into branch 'suppressions'.
Introduce krazy like suppressions
// clazy:skip
https://bugs.kde.org/show_bug.cgi?id=353767
--- Comment #4 from Sergio Martins ---
Pragmas seem too crude, they act on the whole file unless you do a lot of
push/pop.
I'm thinking about a special comment which if present will tell clazy to shut
up, just like we have for krazy
--
You are receiv
https://bugs.kde.org/show_bug.cgi?id=353767
--- Comment #3 from Richard ---
(In reply to Sergio Martins from comment #2)
> (In reply to Richard from comment #1)
> > It would be possible to work with clazy warnings like ordinary compiler
> > warnings?
> > E.g. have them disabled locally with
> >
https://bugs.kde.org/show_bug.cgi?id=353767
--- Comment #2 from Sergio Martins ---
(In reply to Richard from comment #1)
> It would be possible to work with clazy warnings like ordinary compiler
> warnings?
> E.g. have them disabled locally with
>
> #pragma clang diagnostic push
> #pragma clang
https://bugs.kde.org/show_bug.cgi?id=353767
Richard changed:
What|Removed |Added
CC||r.oehlin...@avibit.com
--- Comment #1 from Richard -
