> > not using --library=gtk > > See #1197 for why its needed I'm on my phone so can't ask git for details, but l just added it here, so either I bluntly missed it somehow, or it got removed in the meantime, which would be concerning for re-adding it here…
> ... should we switch to C++ where its all built into the compiler and doesn't > need another tool to apply spurious checks. I'm serious, That's just the C++ grumpy old guy talking, because it's simply not true 😉 Sure C++ has more memory management goodies, but you have to use them in the first place, building the current codebase with a C++ compiler won't magically fix things -- well, it likely won't build without some patching, so in a sense it would avoid all issues… 😂 > > I'm not sure it has any value… does it? > > Oh how tempting ..... nah, I'll be nice. 😜 That's clearly quote misuse… but I laughed, so I give it a pass > My 2c is that most plugins are so poorly maintained that if you add > cppchecking that actually checks much, you will be the one making the > patches. You are just adding to your workload. Hopefully it won't find many more issues in the existing code, but could on new one. Though, it's like with all those imperfect tools, the user has to be able to tell whether a warning is meaningful or not, and how to handle it. -- Reply to this email directly or view it on GitHub: https://github.com/geany/geany-plugins/pull/1346#issuecomment-2088128774 You are receiving this because you are subscribed to this thread. Message ID: <geany/geany-plugins/pull/1346/[email protected]>
