RRDTool VS Cppcheck

RRDTool Reviews

Cppcheck Reviews

RRDTool mentions (3)

• Seeing through hardware counters: a journey to threefold performance increase

  For anyone interested in how the graphs were made: https://oss.oetiker.ch/rrdtool/ Happy to see people still using RRD after all these years. - Source: Hacker News / over 1 year ago

• One of the longest standing soundness holes in Rust -- Diving Deep: implied bounds and variance

  (I actually implemented the firmware for this... Using the Arduino port for ESP8266 because I was impatient, but discovered that either my DHT11 modules are junk or I'm misusing them, because the humidity measurement drifts as they keep running. I need to write the Rust+rrdtool app meant to receive the reports and then do some comparative tests between the DHT11 and some BME280s, and between the current firmware... Source: over 2 years ago

• Arizona in October is solar bliss

  Nice! This is giving me some ideas. Here's what my old school rrdtool-based system looks like:. Source: over 2 years ago

Cppcheck mentions (10)

• Configuring Cppcheck, Cpplint, and JSON Lint

  I dedicated Sunday morning to going over the documentation of the linters we use in the project. The goal was to understand all options and use them in the best way for our project. Seeing their manuals side by side was nice because even very similar things are solved differently. Cppcheck is the most configurable and best documented; JSON Lint lies at the other end. - Source: dev.to / 3 months ago

• Enforcing Memory Safety?

  Using infer, someone else exploited null-dereference checks to introduce simple affine types in C++. Cppcheck also checks for null-dereferences. Unfortunately, that approach means that borrow-counting references have a larger sizeof than non-borrow counting references, so optimizing the count away potentially changes the semantics of a program which introduces a whole new way of writing subtly wrong code. Source: 12 months ago

• Static Code analysis

  For my own projects, I used cppcheck. You can check out that tool to get a feel. Depending on what industry your in, you might need to follow a standard like Misra. Source: about 1 year ago

• How do you not shoot yourself in the foot ?

  Https://cppcheck.sourceforge.io/ (there are many other static analysis tools, I just haven't used them or didn't care for them). Source: about 1 year ago

• Linting tool for prohibiting the use of specific std types

  Sounds like something that could simply be communicated with the team that writes the tests. Unless you have dozens of such classes. In that case, you could just use e.g. Cppcheck and add a rule (regular expression) that searches for usages of the forbidden classes. Source: over 1 year ago