Lines Matching full:nanopb

1 # Nanopb: New features in nanopb 0.4
3 ## What's new in nanopb 0.4
5 Long in the making, nanopb 0.4 has seen some wide reaching improvements
11 compatibility with previous nanopb versions. For a list of breaking
16 The basic design of nanopb has always been that the information about
21 In nanopb-0.3.0 the field iteration logic was separated to
44 Previously nanopb was quite RAM-heavy on AVR, which cannot put normal
49 Nanopb generator is now available as a Python package, installable using
52 `pip install nanopb` and have the generator available on path as
61 Initially, nanopb generator was used in two steps: first calling
66 Nanopb 0.2.3 added support for running as a `protoc` plugin, which
68 the plugin mode has two complications: passing options to nanopb
79 Since its very beginnings, nanopb has supported field callbacks to allow
90 Nanopb-0.4.0 introduces callbacks that are referenced by the function
102 [tests/oneof_callback](https://github.com/nanopb/nanopb/tree/master/tests/oneof_callback) test case…
103 [examples/network_server](https://github.com/nanopb/nanopb/tree/master/examples/network_server) exa…
119 There is an example of this in [tests/oneof_callback](https://github.com/nanopb/nanopb/tree/master/…
124 got it wrong. But since nanopb 0.2, the field descriptor generation has
138 extent, and nanopb will automatically detect the size and position of
146 codepoints. Previously nanopb has not enforced this, requiring extra
159 Now that example is integrated as an optional feature in nanopb core. By
171 Nanopb fuzzer has also been integrated in Google's [OSSFuzz](https://google.github.io/oss-fuzz/)