lib/qcbor/README.md

31   context is 176 bytes, decode context is 312 bytes and the
34   encoded CBOR and encode/decode contexts so caller has full control
38 **Easy decoding of maps** – The "spiffy decode" functions allow
71 These are functions to decode particular data types. They are an
75 Spiffy decode supports easier map and array decoding. A map can be
80 An internal error state is maintained. This simplifies the decode
82 decode, rather than on every function.
106 The spiffy decode functions will handle definite and indefinite length
136 decode function. In many cases the error check is only needed as the
137 last step or an encode or decode. TinyCBOR requires an error check on
389     | decode only   |     1550 |   13300 |
408  setup to decode indefinite-length strings adds 0.5KB.
410  Basic use of spiffy decode to brings in about 3KB. Using more spiffy
411  decode functions, such as those for tagged types bstr wrapping brings
462 The QCBOR decode API processes both definite and indefinite lengths
463 with the same API, except to decode indefinite-length strings a
494  ### Size of spiffy decode
496  When creating a decode implementation, there is a choice of whether
497  or not to use spiffy decode features or to just use
500  The implementation using spiffy decode will be simpler resulting in
502  from the QCBOR library will be larger. Basic use of spiffy decode
504  concern, then it is probably better to use spiffy decode because it
511  spiffy decode may reduce overall code size.  An example of a complex
514  because the general purpose spiffy decode map processor is the one