Daniel Marjamäki
Daniel Marjamäki
@Tal500 I did not see such information when I started implementing simplecpp and therefore I implemented the macro expansion using trial and error. So it wasn't that I _wanted_ to...
> As macos-14 is using the ARM-based M1 processor I would like to include that as we currently only perform builds for x86-based platforms. :+1:
@Tal500 can you please simplify the examples. The code `int foo() {` is not handled during the preprocessing and can be removed. I prefer if you just show the relevant...
> Can we merge this in? As I cannot build cppcheck locally on my mac. this is BAD. :-( do you think it's possible to reproduce on a macos-latest runner...
> do you think it's possible to reproduce on a macos-latest runner or something? I have a macincloud account. Unfortunately I don't have cmake and don't have permissions to install...
@firewave would you like assistance with that MISRA warning? The dumpfile contains the macroname nowadays so it's possible to tweak the misra.py script to still detect the violation.
@firewave could you explain the overall problem with generating a DLL that is reused by both the GUI and CLI? It sounds like a good idea to me technically to...
> I always found it strange that library.h depended on the ValueFlow. yes :+1:
> I think this change is OK, since it doesn't involve the library, and `isAttributeConst()` is not ambiguous. I agree
@pfultz2 I hope you can take another look if you are happy now..