9 Mar
2020
9 Mar
'20
1:26 p.m.
The "Shitty API" is not having constructors and destructors, and relying on the user to call a function to "free" some resources instead of having their lifetime managed automatically via RAII. Anyway... this has veered off-topic. You came close to discussing the topic when you linked this library wrapper: <https://github.com/do-m-en/libarchive_cpp_wrapper> But you didn't actually discuss its API and the suitability to zlib. Looking over this library I see: template<ns_writer::format FORMAT, ns_writer::filter FILTER> static writer make_writer(std::ostream& stream, size_t block_size); Are you suggesting that ZLib should use ostream and istream as the interface for writing and reading data? Thanks