Oliver Stöneberg

Results 1147 comments of Oliver Stöneberg

Safety: Make the interface safer by removing old style C buffer inputs

> I have the feeling that the Tokenizer in Cppcheck could be 90% faster if we redesign it. The speed of that is fine (except for some extreme cases) -...

Safety: Make the interface safer by removing old style C buffer inputs

> Anyway it feels like `std::vector` would be better than `std::string` from a type safety point of view to distinguish that it's raw file data not a string. That is...

Safety: Make the interface safer by removing old style C buffer inputs

We should keep in mind that this was not based on an external request. I will obviously over-engineer this from the start and I think it will help to come...

Safety: Make the interface safer by removing old style C buffer inputs

There is also #279 regarding performance which is a much more general issue.

Safety: Make the interface safer by removing old style C buffer inputs

> I wonder if you have ever profiled simplecpp in windows. Yes, but not much since enough still falls out of simply doing it on Linux. Also it is confusing...

Safety: Make the interface safer by removing old style C buffer inputs

Closed in favor of #496.

`line number out of bounds` error notification shown for `valueFlowMaxIterations`

This is another type of message which should be shown at the file-level - see #60. The notification is shown because this unlike others is currently not explicitly handled in...

error might be stuck even after file modification

![image](https://github.com/user-attachments/assets/7a30266d-be6f-458b-bd35-738cf3e870e6)

error might be stuck even after file modification

A way to fix this is to `CTRL+A`, `CTRL+X`, `CTRL+V` the contents of the file.

fixed #10697 - split `unmatchedSuppression` from `--enable=information`

First of all `unmatchedSuppression` has probably never worked properly. So depending on your configuration it might have been that have never seen such a warning at all or you had...