lib/qcbor/README.md

24   worry so much about this and so code using QCBOR passes static
25   analyzers easier.  Simpler code because there is no support for
57 **Small code size** – In the smallest configuration the object
58   code is less than 4KB on 64-bit x86 CPUs. The design is such that
59   object code for QCBOR APIs not used is not referenced.
85 many fewer lines of code. They also tend to parallel the encoding
126 No detailed code size comparison has been made, but in a spot check
129 larger. This includes the code to call the library, which is about the
130 same for both libraries, and the code linked from the libraries. QCBOR
131 is a bit more powerful, so you get value for the extra code brought
135 doesn't have to check the return code of every call to an encode or
143 items with duplicate labels. This makes the code for decoding CBOR
144 simpler, similar to the encoding code and easier to read. TinyCBOR
217 While this code will run fine without configuration, there are several
221  * to reduce code size
223  * remove features to reduce code size
282 used to reduce object code size and dependency.
319 request floating-point conversion, an error code like
322 This saves only a small amount of object code. The primary purpose for
339 The primary reason to define this is to save object code.
354 which float-point related code is generated. For example,
392  From the table above, one can see that the amount of code pulled in
396  interdependency so only code necessary for the called functions is
400  bring in only 1KB of code.
402  Encoding of floating-point brings in a little more code as does
412  in more code.
416  QCBORDecode_GetInt64() without bringing in very much code.
419  ways to make the code smaller.
425  code because Usefulbuf provides similar defenses and this code was
429  copy of the code is in memory no matter how many applications use it.
434 code. The amount saved is an approximation.
501  the calling code being smaller, but the amount of code brought in
503  brings in about 2KB of object code.  If object code size is not a
508  If code size is a concern, then use of QCBORDecode_GetNext() will
509  probably result in smaller overall code size for simpler CBOR
511  spiffy decode may reduce overall code size.  An example of a complex
513  have many data items in them.  The overall code may be smaller
555 * Redistributions of source code must retain the above copyright