mpack icon indicating copy to clipboard operation
mpack copied to clipboard

MPack - A C encoder/decoder for the MessagePack serialization format / msgpack.org[C]

Results 11 mpack issues
Sort by recently updated
recently updated
newest added

I copied the "amalgamation package" sources to my project and compiled it with a STM32 CubeIDE compiler. Got some warnings about incompatible types: ```log format '%u' expects argument of type...

There's another project (since 2016) with a similar name: https://github.com/libmpack/libmpack Would be useful to see it in your comparison table: https://github.com/ludocode/mpack#comparison-with-other-parsers I also wonder if the names are too similar?...

documentation only

Hi, I really like how well this library is developed and might want to use it in a project. However, I'm not sure if the node reader API can be...

feature request

hi, I ran into a segfault with the following code: ```c mpack_writer_t writer; char *output_data = nullptr; size_t output_size = 0; mpack_writer_init_growable(&writer, &output_data, &output_size); const int N_OUTER = 10; const...

fixed; needs better tests

Taking the example from the README: ```c #include #include #include int main() { char* data; size_t size; mpack_writer_t writer; mpack_writer_init_growable(&writer, &data, &size); // write the example on the msgpack homepage...

fixed; needs better tests

Hello, I'm testing the MPack library in an ESP32-C3 microcontroller. Below the code I'm using for testing (I added the MPack functions in the app_main function): ``` #include #include #include...

Listing all targets using ```tools/unit.sh help``` not work. To make this work, the 524 line in the configure.py need to me changed from: ```out.write(" command = cat .build/help\n")``` to ```out.write("...

Hi, Parts of this may have been touched on in #100 but I wanted to start a clean discussion here. I'm trying to redesign an RPC-like protocol to use MessagePack....

All of the functions that operate on files, such as `mpack_reader_init_filename` store the file handle in the custom context. This means that the context can't be set by the user...

Hi. It seems whatever data I write with mapck_writer_t, it always gives mpack_error_memory. Is it not compaible with AVR?