fix error when __STDC_VERSION__ is not defined

Add missing uint32_t casts (#385)

Add C++ message descriptors helper

Zero-overhead. Allows creating simpler general nanopb C++ wrappers by
examining variable type and not needing macro magic.

Build fixes for Microsoft VC++

Rename #define fieldname_default to _DEFAULT to avoid conflict with older constant.

This should make migration error messages less confusing.

Add descriptorsize option.

Allow specifying a per-message callback.

This allows callbacks to be combined with oneofs and pointer fields (#175)

Combine new per-msg encode/decode callbacks to one field_callback.

This seems like it will result in less boilerplate in typical situations
where a specific message is either decoded or encoded. Otherwise it would
result in lots of dummy functions like:

bool MyQuery_encode_callback(...)
{
return false; /* MyQuery is never encoded */
}

Prepare for moving callback pointer to pb_msgdesc_t.

Add static asserts to check that field values fit in descriptor.

New field descriptor format.

Now field information is stored as a variable-length uint32_t array.
This reduces the minimum size in most cases:

old new
basic field: 10 bytes 4 bytes
repeated field: 10 bytes 8 bytes
field with 12bit tag/size: 16 bytes 8 bytes
field with 16bit tag/size: 16 bytes 16 bytes
field with 32bit tag/size: 28 bytes 16 bytes

Further, now the descriptor size can be increased per-field and per-message,
instead of previous global PB_FIELD_16BIT and PB_FIELD_32BIT.

PB_FIELD_32BIT still affects the pb_size_t type, which is 16-bit by default.

Setting version to 0.4.0-dev

Publishing nanopb-0.3.9.2

Fix decoding of non-packable fixed count repeated fields

Allow fixed count repeated values

Setting version to 0.4.0-dev

Publishing nanopb-0.3.9

Add option to build without 64-bit support (issue #86)

Check CHAR_BIT before using optimized pb_decode_fixedXX() version

Set version to nanopb-0.4.0-dev

Setting version to 0.3.9-dev

Publishing nanopb-0.3.8

Extend inline / fixed length bytes array support (issue #244)

Adds support for proto3 and POINTER field types to have
fixed length bytes arrays. Also changed the .proto option
to a separate fixed_length:true, while also supporting the old FT_INLINE
option.

Restructured the generator and decoder logic to threat the inline
bytes fields more like "just another field type".

Zero-valued extension fields were mistakenly ignored by encoder. (issue #242)

Fix multiple oneofs in same message (issue #229)

Previously the field iterator logic didn't know whether two
oneof fields were part of the same union, or separate. This
caused wrong pointers to be calculated if multiple oneofs were
inside a single message.

This commit fixes this by using dataoffset of PB_SIZE_MAX to
indicate union fields after the first field.

Theoretically PB_SIZE_MAX is also a valid value for data offset,
which could cause errors. Adding a compile-time assert for this
is somewhat difficult. However I consider it extremely unlikely
that there is any platform that could trigger this situation, as
it would require 255 bytes of extra data/padding between two protobuf
oneof fields. On 64-bit architectures the worst case is 16 bytes,
and even esoteric platforms only align to 64 bytes or so. Manual
modification of the generated .pb.h file could trigger this, but
even then it would require pretty bad luck to happen.

Setting version to 0.3.8-dev

Publishing nanopb-0.3.7

Add proto3 option to handle singular fields

Add inline allocation of bytes fields

This commit adds a new FT_INLINE allocation type that forces bytes
fields to be inlined into the struct. E.g., pb_byte_t my_bytes[32].
This requires max_size for the bytes field. The FT_INLINE type is
represented as a new LTYPE: FT_LTYPE_FIXED_LENGTH_BYTES.

This commit also updates the documentation with FT_INLINE and
FT_LTYPE_FIXED_LENGTH_BYTES.

Added an AUTHORS file in apparent order of appearance in the git log
history from $(git log --all).

Setting version to 0.3.7-dev

Publishing nanopb-0.3.6

Setting version to 0.3.6-dev

Publishing nanopb-0.3.5

Remove obsolete __BIG_ENDIAN__ compilation option.

This is now handled automatically using shift operations.

Replace uint8_t with a pb_byte_t typedef.

This supports platforms where uint8_t does not exist.
If you are using a custom pb_syshdr.h, this may require adding
definitions for uint_least8_t etc.

Modify the int size STATIC_ASSERTS to work with CHAR_BITS!=8.

This will still catch the most common bug of long int vs. long long int.
The uint8_t checks do not seem necessary, test for this will be added
in later commit.

Add testcase for anonymous unions + few fixes.

Fixes compilation error with anonymous unions when
it is not the last field in message. Also fixes
extraneous newlines in header file. Cleanup the
pb.h extraneous use of ##.

Add option to allow for anonymous unions

Setting version to 0.3.5-dev

Publishing nanopb-0.3.4

Fix handling of unsigned 8- or 16-bit enums.

Previously unsigned enums would throw errors on decoding if the value
went outside the signed range (issue #164).

Currently only helps for enums defined within the same file, but solving
issue #165 will make it work for multiple files also.

Setting version to 0.3.4-dev

Publishing nanopb-0.3.3

Setting version to nanopb-0.3.3-dev

Publishing nanopb-0.3.2

Bugfixes for oneof support.

Fixes crashes / memory leaks when using pointer type fields.
Also fixes initialization of which_oneof fields.

Implement support for oneofs (C unions).

Basic test included, should probably add an oneof to the AllTypes test also.

Update issue 131
Status: Started

Change PB_RETURN_ERROR() macro to avoid compiler warnings.

Update issue 140
Status: FixedInGit

Add support for POINTER type in extensions

Add compilation option to disable struct packing.

Update issue 136
Status: FixedInGit

Set version to nanopb-0.3.2-dev

Publishing nanopb-0.3.1

Setting version to 0.3.1-dev

Publishing nanopb-0.3.0

Add #if guard for .pb.h version.

The version in PB_PROTO_HEADER_VERSION can be bumped whenever there
is a breaking change to the generated files, and it will then alert
to the difference.

Update issue 129
Status: FixedInGit

Rename poorly named identifier to avoid name conflicts.

Update issue 106
Status: FixedInGit

Rename UNUSED() and STATIC_ASSERT() macros with PB_ prefix.

This avoids possible namespace conflicts with other macros.

Change the _count fields to use pb_size_t datatype.

Update issue 82
Status: FixedInGit

Setting version to 0.3.0-dev

Publishing nanopb-0.2.9

Add PB_PACKED_STRUCT support for Keil MDK-ARM toolchain

Patch from Jon Read.

Update issue 119
Status: FixedInGit

Setting version to 0.2.9-dev

Publishing nanopb-0.2.8

Setting version to 0.2.8-dev

Publishing nanopb-0.2.7

Fix unused parameter warning when building without errmsg.

Add a 'found' field to pb_extension_t.

Update issue 112
Status: FixedInGit

More configuration options for dynamic alloc

Get rid of pb_bytes_ptr_t, just allocate pb_bytes_array_t dynamically.

This makes the internal logic much simpler, and also keeps the datatypes
more similar between STATIC/POINTER cases. It will still be a bit cumbersome
to use because of variable length array member. Macros PB_BYTES_ARRAY_T(n) and
PB_BYTES_ARRAY_T_ALLOCSIZE(n) have been added to make life a bit easier.

This has the drawback that it is no longer as easy to use externally allocated
byte array as input for bytes field in pointer mode. However, this is still
easy to do using callbacks, so it shouldn't be a large issue.

Beginnings of malloc support in pb_decode

Setting version to 0.2.7-dev

Publishing nanopb-0.2.6

Add coments to places where STATIC_ASSERT is used.

Update issue 96
Status: FixedInGit

Setting version to 0.2.6-dev

Publishing nanopb-0.2.5

Organize allocation logic in generator, add pb_bytes_ptr_t.

Allocation decision is now made before the field data type is decided.
This way the data type decisions can more cleanly account for the allocation
type, i.e. FT_DEFAULT logic etc.

Added pb_bytes_ptr_t for pointer-allocated bytes-fields. There is no point
generating separate structs for these, as they would all be of the same type.

Generating and encoding messages with dynamic allocaiton

Add PB_LTYPE_UVARINT to fix encoding of negative int32 values.

Apparently int32 values that are negative must be cast into int64 first
before being encoded. Because uint32 still needs to be cast to uint64,
the cases for int32 and uint32 had to be separated.

Update issue 97
Status: FixedInGit

Setting version to 0.2.5-dev

Publishing nanopb-0.2.4

Define pb_size_t and pb_ssize_t data types.

Use these in pb_field_t definition to clean up some #ifs, and also
to prepare for solving issue #82.

Setting version to 0.2.4-dev

Publishing nanopb-0.2.3

Fine-tune the naming of new macros before merging into master.

Requires re-generation of files generated with dev_get_rid_of_ternary_operator.

Get rid of the ternary operator in the pb_field_t initialization.

Some compilers where unable to detect that the ternary operator
can be evaluated at the compile time. This commit does the evaluation
on the Python side, which should fix the problem.

The new .pb.c files are generated using PB_FIELD2() macro. The old
PB_FIELD() macro remains, so that previously generated files keep
working.

Add an example pb_syshdr.h file for platforms without C99.

This allows building the tests easily on Visual C++ in C mode.

Also add checks to pb.h that the defined integer types are of
the proper sizes. This may prevent some difficult to debug problems
later..

Setting version to 0.2.3-dev

Publishing nanopb-0.2.2

Fix bugs in extension support when multiple extension fields are present.

Implement extension support for the encoder

Implement generator support for extension fields (no encoder/decoder support yet)

Add section in pb.h for changing compilation settings.

Update issue 76
Status: FixedInGit

Setting version to 0.2.2-dev

Publishing nanopb-0.2.1

__pragma keyword is only supported by recent Microsoft compilers

Change the callback function to use void**.

NOTE: This change breaks backwards-compatibility by default.
If you have old callback functions, you can define PB_OLD_CALLBACK_STYLE
to retain the old behaviour.

If you want to convert your old callbacks to new signature, you need
to do the following:

1) Change decode callback argument to void **arg
and encode callback argument to void * const *arg.

2) Change any reference to arg into *arg.

The rationale for making the new behaviour the default is that it
simplifies the common case of "allocate some memory in decode callback".

Update issue 69
Status: FixedInGit

Fix warning on clang.

Update issue 67
Status: FixedInGit

Add support for packed structures on IAR and MSVC.

Update issue 66
Status: FixedInGit

Add PB_SYSTEM_HEADER compile time option.

This allows replacing the C99 standard include file names with
a single system-specific file. It should provide all the necessary
system functions (typedefs, memset, memcpy, strlen).

Update issue 62
Status: FixedInGit

Setting version to 0.2.1-dev

Publishing nanopb-0.2.0

Separate PB_HTYPE to PB_ATYPE and PB_HTYPE.

Also clean up the logic so that it is easier to implement more
allocation types in the future.

Update issue 53
Status: FixedInGit

Rename PB_HTYPE_ARRAY -> PB_HTYPE_REPEATED.

This is a more logical name in parallel with PB_HTYPE_REQUIRED and PB_HTYPE_OPTIONAL.

Warning: This breaks backwards-compatibility of generated .pb.c files.
You will have to regenerate the files and recompile.

Reformat generated .pb.c files using macros.

This has the following advantages:
1) Easier to modify pb_field_t encoding
2) Simpler generator logic
3) Tidier looking, easier to read .pb.c files

Update issue 58
Status: FixedInGit

Setting version to 0.1.9.1-dev

Publishing nanopb-0.1.9

Replace pb_type_t enum with #defines.

See issue #57.

Set version to 0.2.0-dev

Fix misleading comment (current generator sets LTYPE always).

Setting version to 0.1.9-dev

Publishing nanopb-0.1.8

Rename test_compiles.c to test_multiple_files.c

Fix STATIC_ASSERT macro when using multiple .proto files.

The __COUNTER__ macro (used for generating unique names) is at least supported
by gcc, clang and Visual Studio. With this change test_compiles.c is
compilable, since no more typedefs are redefined.

Compilers/Preprocessors not supporting __COUNTER__ error's are still possible
which are hopfully handled by the usage of __LINE__ in most sittuations.

Added unit test for the problem.

Setting version to 0.1.8-dev

Publishing nanopb-0.1.7

Add nanopb version number to generated files.

tools/set_version.sh is used to update the values.

Update issue 36
Status: FixedInGit

Give names to generated structures to allow forward declaration.

Update issue 39
Status: FixedInGit

Enable -Wconversion for core and fix the warnings.

This should help avoid issue 33 in the future.

Fix -Wextra warning in generated .pb.c files.

Compile the generated files with the same extra-strict
settings as the core, in order to detect problems in tests.

Update issue 32
Status: FixedInGit

Implement error messages in the decoder side.

Update issue 7
Status: Started

Replace #warning with the standard #error.

Cast enum vaules to integers and cast them back where appropraite
to prevent mixed enumeration type compiler warnings

Replace PB_MANY_FIELDS with PB_FIELD_16BIT and PB_FIELD_32BIT.

This allows more precise control over the memory use vs. field size.

Add PB_MANY_FIELDS option for supporting fields > 255.

Add generator warning if this is necessary.
Fixes issue #14.

Improve the detection of missing required fields.

Now the limit of tracked fields is configurable at compile-time using
PB_MAX_REQUIRED_FIELDS. Added related test and updated documentation.

Fixes issue #18.

Fixing compiler warnings, mostly related to unused parameters.

Thanks to David Hotham for the patch. Fixes issue 8.

Merged 0004-Added-missing-trailing-newlines.patch by Matt Kern.
Just adding newlines at the end of files to satisfy old GCC versions.


git-svn-id: https://svn.kapsi.fi/jpa/nanopb@1021 e3a754e5-d11d-0410-8d38-ebb782a927b9

Fixed a bunch of bugs related to callback fields.

Most importantly, callback fields in submessages were being overwritten with garbage, causing segfaults.

Additionally, converted PB_LTYPE_FIXED to PB_LTYPE_FIXED32 and PB_LTYPE_FIXED64. This makes the interface
a bit easier to use, and in addition runs faster.


git-svn-id: https://svn.kapsi.fi/jpa/nanopb@975 e3a754e5-d11d-0410-8d38-ebb782a927b9

Example

git-svn-id: https://svn.kapsi.fi/jpa/nanopb@957 e3a754e5-d11d-0410-8d38-ebb782a927b9

More documentation, small improvements

git-svn-id: https://svn.kapsi.fi/jpa/nanopb@955 e3a754e5-d11d-0410-8d38-ebb782a927b9

Started writing documentation

git-svn-id: https://svn.kapsi.fi/jpa/nanopb@953 e3a754e5-d11d-0410-8d38-ebb782a927b9

Encoder

git-svn-id: https://svn.kapsi.fi/jpa/nanopb@951 e3a754e5-d11d-0410-8d38-ebb782a927b9

First version of header generator

git-svn-id: https://svn.kapsi.fi/jpa/nanopb@950 e3a754e5-d11d-0410-8d38-ebb782a927b9

unittests (some)

git-svn-id: https://svn.kapsi.fi/jpa/nanopb@949 e3a754e5-d11d-0410-8d38-ebb782a927b9

git-svn-id: https://svn.kapsi.fi/jpa/nanopb@947 e3a754e5-d11d-0410-8d38-ebb782a927b9

Making code ansi-compatible

git-svn-id: https://svn.kapsi.fi/jpa/nanopb@944 e3a754e5-d11d-0410-8d38-ebb782a927b9

Improvements, array support

git-svn-id: https://svn.kapsi.fi/jpa/nanopb@943 e3a754e5-d11d-0410-8d38-ebb782a927b9

First version of decoding

git-svn-id: https://svn.kapsi.fi/jpa/nanopb@942 e3a754e5-d11d-0410-8d38-ebb782a927b9