Jansson VS ZLib

I'm a fan of jansson easy to use and great documentation

Context: I needed to emit rather complex compound JSON data for a C-based project I'm working on. I could do it all with sprintf(), but it got messy quickly. I looked at available libraries such as jansson and CCAN's json, but they both used malloc(), which isn't an option in my case.

I find jansson quite usable and minimal: https://github.com/akheron/jansson

JanSON has been really good for my uses. Simple, intuitive, fast.

I don't see why something like Jansson wouldn't.

Jansson - Library for encoding, decoding and manipulating JSON. MIT

A fix has been checked into the upstream git repo: https://github.com/madler/zlib/pull/843 but a release has not yet been made including it.

So the real issue here is that the lack of tree validation before the tree construction, I believe. I'm surprised that this check was not yet implemented (I actually checked libwebp to make sure that I was missing one). Given this blind spot, an automated test based on the domain knowledge is likely useless to catch this bug.

[1] https://github.com/madler/zlib/blob/master/examples/enough.c

In the source code of the Node.js opensource project, lib folder contains JavaScript code, mostly wrappers over C++ and function definitions. On the contrary, src folder contains C++ implementations of the functions, which pulls dependencies from the V8 project, the libuv project, the zlib project, the llhttp project, and many more - which are all placed at the deps folder.

Seeing the text in red got me thinking for a moment, "wow, didn't realize pirates had such love for an open-source compression library"

cd "${srcdir}/zlib-$pkgver/contrib/minizip" make install DESTDIR="${pkgdir}" install -D -m644 "${srcdir}/zlib-$pkgver/LICENSE" "${pkgdir}/usr/share/licenses/minizip/LICENSE" # https://github.com/madler/zlib/pull/229 rm "${pkgdir}/usr/include/minizip/crypt.h"