diff options
| author |   Petteri Aimonen <jpa@git.mail.kapsi.fi> | 2016-08-06 10:42:04 +0300 |
|---|---|---|
| committer | Petteri Aimonen <jpa@git.mail.kapsi.fi> | 2016-08-06 10:42:04 +0300 |
| commit | bc2c47ef77a29e7efdaf088b9a0f7bf15a53c976 (patch) | |
| tree | 77e7ee191b2756e139c4fe13b3fd0e18aee1adcf | |
| parent | 68a86e96481e6bea987df8de47027847b30c325b (diff) | |
Fix formatting error in docs
| -rw-r--r-- | docs/concepts.rst | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/concepts.rst b/docs/concepts.rst index c43d8299..ef880cff 100644 --- a/docs/concepts.rst +++ b/docs/concepts.rst @@ -149,7 +149,7 @@ Most Protocol Buffers datatypes have directly corresponding C datatypes, such as 1) Strings, bytes and repeated fields of any type map to callback functions by default. 2) If there is a special option *(nanopb).max_size* specified in the .proto file, string maps to null-terminated char array and bytes map to a structure containing a char array and a size field. 3) If *(nanopb).type* is set to *FT_INLINE* and *(nanopb).max_size* is also set, then bytes map to an inline byte array of fixed size. -3) If there is a special option *(nanopb).max_count* specified on a repeated field, it maps to an array of whatever type is being repeated. Another field will be created for the actual number of entries stored. +4) If there is a special option *(nanopb).max_count* specified on a repeated field, it maps to an array of whatever type is being repeated. Another field will be created for the actual number of entries stored. =============================================================================== ======================= field in .proto autogenerated in .h |