diff options
author | Petteri Aimonen <jpa@git.mail.kapsi.fi> | 2019-06-01 09:45:21 +0300 |
---|---|---|
committer | Petteri Aimonen <jpa@git.mail.kapsi.fi> | 2019-06-01 09:45:21 +0300 |
commit | 92033ba4f629ad859683f27fd18dcffff39be88c (patch) | |
tree | 0d204cdb90b454b95ed4db7833b3c216da1165ed /docs | |
parent | 0381b5f0abaa0c627a8ee8291f1281f97aec5d6c (diff) | |
download | nanopb-c-92033ba4f629ad859683f27fd18dcffff39be88c.tar.gz |
Add migration note about enum min/max
Diffstat (limited to 'docs')
-rw-r--r-- | docs/migration.rst | 19 |
1 files changed, 18 insertions, 1 deletions
diff --git a/docs/migration.rst b/docs/migration.rst index fdc1d8c..a1843e3 100644 --- a/docs/migration.rst +++ b/docs/migration.rst @@ -11,7 +11,24 @@ are included, in order to make it easier to find this document. .. contents :: -Nanopb-0.3.9.1, 0.4.0 (2018-xx-xx) +Nanopb-0.3.9.4, 0.4.0 (2019-xx-xx) +================================== + +Fix generation of min/max defines for enum types +------------------------------------------------ + +**Rationale:** Nanopb generator makes #defines for enum minimum and maximum +value. Previously these defines incorrectly had the first and last enum value, +instead of the actual minimum and maximum. (issue #405) + +**Changes:** Minimum define now always has the smallest value, and maximum +define always has the largest value. + +**Required actions:** If these defines are used and enum values in .proto file +are not defined in ascending order, user code behaviour may change. Check that +user code doesn't expect the old, incorrect first/last behaviour. + +Nanopb-0.3.9.1, 0.4.0 (2018-04-14) ================================== Fix handling of string and bytes default values |