Question 1

How do I use CMP to serialize data to a socket?

Accepted Answer

Implement read/write/skip functions that call socket APIs, similar to the file example in the README. CMP's flexible backend allows any data source, but you need to handle the socket operations manually, including error checking and buffering.

Question 2

CMP vs msgpack-c: which should I use?

Accepted Answer

CMP is lighter with zero allocations and pure C, ideal for embedded systems or minimal setups. msgpack-c offers more features like C++ support and a larger ecosystem. Choose CMP for control and portability, msgpack-c for convenience and broader integration.

Question 3

Does CMP support floating point numbers?

Accepted Answer

Yes, but floating point operations can be disabled by defining CMP_NO_FLOAT, which changes the ABI. This is useful for systems without FPU support, but it requires careful consideration if ABI stability is important.

Question 4

Is CMP thread-safe?

Accepted Answer

Yes, contexts are thread-local, so each thread can use its own context safely without synchronization. However, contexts cannot be shared between threads, as stated in the README.

Question 5

How to handle backward compatibility with MessagePack v4?

Accepted Answer

Avoid using bin-related functions and use the v4-specific functions like cmp_write_str_v4, as detailed in the backwards compatibility section. This ensures interoperability with older implementations that don't support the BIN type.

Question 6

What compilers does CMP work with?

Accepted Answer

CMP is tested with clang and GCC using strict flags like -Wall -Werror, and it's written in portable C89, so it should work with most standard-compliant C compilers. The test suite requires C99, but the library itself doesn't.

cmp

What is cmp?

Overview

Use Cases

Best For

Related Projects

Found a gem we're missing?

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions