protozero - npm Package Compare versions

Comparing version 1.4.5 to 1.5.0

package.json

		{
		"name": "protozero",
		"version": "1.4.5",
		"version": "1.5.0",
		"description": "Minimalist protocol buffer decoder and encoder in C++",
		@@ -5,0 +5,0 @@ "main": "include_dirs.js",

README.md

		@@ -51,5 +51,5 @@ # protozero
		Protozero.
		* Some advanced topics are described in an [extra document](doc/advanced.md).
		* There is a table of all types and functions in the
		[cheat sheet](doc/cheatsheet.md).
		* [Macros defined or used by Protozero](doc/macros.md).
		* Read the [upgrading instructions](UPGRADING.md) if you are upgrading from
		@@ -69,17 +69,2 @@ an older version of Protozero.

		## Limitations

		* A protobuf message has to fit into memory completely, otherwise it can not
		be parsed with this library. There is no streaming support.
		* The length of a string, bytes, or submessage can't be more than 2^31-1.
		* The Google Protobuf spec documents that a non-repeated field can actually
		appear several times in a message and the implementation is required to
		return the value of the last version of that field in this case.
		`pbf_reader.hpp` does not enforce this. If this feature is needed in your
		case, you have to do this yourself.
		* There is no specific support for maps but they can be used as described in
		the "Backwards compatibility" section of
		https://developers.google.com/protocol-buffers/docs/proto3#maps.


		## Endianness
		@@ -86,0 +71,0 @@

include/protozero/pbf_builder.hpp