Hello,
First for my 2 cents, I do have it locally installed in a docker
container and I use it from time to time. Some checks (like typos) are
still worthwhile. Some other are obsoleted by Clazy and some other are
dubious in 2019/C++17. Nevertheless I always loved that this tool
existed and used it a few time over the years to convince managers
that spending time on some projects technical debt was worth it. So
thanks for all this work.
But this isn't the point I want to make in this email. Maybe the
problem isn't the tool (Krazy2) but rather the delivery (EBN). In this
day and age, all the cool kids use CI to pre-merge-lint their work. Be
it GitLab/GitHub/Phab/Jenkins/Gerrit, it is possible for tools to
comment on patches (and even provide fixits). If the
ClangTidy/Clazy/Krazy/-Wextra/Asan/Coverity/CppCheck warnings were
integrated into people workflow, they would not be as easy to
overlook/ignore/not_know/forget.
So maybe EBN can and should be retired, but only if the valuable
warnings get integrated into the "modern workflow" of KDE. Be it Phab
(sigh...) or GitLab (pretty please).
Regards,
Emmanuel Lepage
On Tue, 26 Mar 2019 at 16:16, Allen Winter wrote:
>
> I was notified today that the Krazy runs on the EBN have been stuck (due to a
> stale lockfile)
> for over 3 months. Is this an indication that nobody looks at the EBN
> reports any longer?
>
> I still maintain Krazy and am happy to make modifications, but I don't see
> the point
> unless someone actually reads and acts on the reports.
>
> Note that clazy does replace Krazy on most everything (C++) so it could
> very well be that people are relying on Clazy instead of Krazy.
>
> This is not about the API dox generation side of things, which of course we
> keep.
>
> But has the EBN code and documentation checking service out lived its
> usefulness?
> Shut it down?
>
>
>
>
>
>
>
