Cppcheck VS libvips

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.

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.

Also check out (cppcheck)[https://github.com/danmar/cppcheck] if you want more static analysis

My browser refuses to open that link. This is better: https://github.com/danmar/cppcheck

cppcheck - Extensible C/C++ static analyzer focused on finding bugs.

and five C/C++ static code analyzers: * clang-tidy * oclint * cppcheck * cpplint (recently added!) * include-what-you-use (recently added!)

Start by feeding your codebase to a static analysis tool like cppcheck, to rule out obvious bound-checking mistakes in it.

Cppcheck is free. I've previously used it with a C++ project.

After some research, I found libvips, a demand-driven, horizontally threaded image processing library. It is designed to run quickly while using as little as memory as possible.

Sharp is a fast and efficient image optimization Node.js module that makes use of the native libvips library.

h2non/bimg can handle both if the underlying libvips is compiled with support for both formats.

if you're using linux (which it doesn't seem so) there's also vispdisp https://github.com/jcupitt/vipsdisp which is based on https://github.com/libvips/libvips which will likely take over how images are decoded in the future for everything, at least methodology wise.

The magic happens by way of a library called Libvips, which contains an ultra-high-speed low-memory image resizer.

imagor uses one of the most efficient image processing library libvips. It is typically 4-8x faster than using the quickest ImageMagick and GraphicsMagick settings.

Try the solutions here: https://github.com/libvips/libvips/issues/2479

in that case maybe take a look at https://github.com/libvips/libvips

libvips v8.6+ or ImageMagick for image analysis and transformations