Thiago Macieira

Ok, I've updated the main and dev branches (they're now in sync) with 0.6. The last release of 0.5 is done. Can I ask you to retarget this to dev...

Like I said, this is a good idea. I'll see if I have time to implement this soon. If not, it shouldn't be too difficult to do it. It's basically...

Looks like your C99 support library (`inttypes.h`) is broken. Can you try to compile this simple application and let me know of the results: ```c #include #include #include #include int...

> Is there any progress on this? I'm looking to add tinycbor to [vcpkg](https://github.com/microsoft/vcpkg) and I think this is necessary.. I'm not good at CMake, so it's hard for me...

Right, half-float is often used for storage only, while all the manipulation is done on single- or double-precision. I agree on adding those functions, but let's put each pair on...

Yes, it looks very good. I have one overall comment and two very minor. Overall, I think the `float` API has more value than `double`. Any system capable of double-precision...

Let's do bit manipulation directly. I wonder if there's a `#define` that helps us know that FP is IEEE 754. C++ has that.

If that produces proper results, that's fine. I was thinking of converting the `uint16_t` to `uint32_t` first, then `memcpy` from that to a `float`, instead of doing FP calculations. If...

CBOR is defined as carrying IEEE754 binary64, binary32 and binary16 content. So I like your idea. I don't think we need to provide the `uintXX_t` version of the APIs for...

I don't think we need the `..._as_double` API. Conversion from double to float can be done by user code before reaching TinyCBOR API.