protozero changelog

Changelog History

Page 1

• v1.7.0 Changes

  June 08, 2020

  ➕ Added

  • 👌 Support for buffer types other that std::string. pbf_writer is now just a typedef for basic_pbf_writer<std::string>. Other buffer types can be used with basic_pbf_writer. See doc/advanced.md for details.

  🔄 Changed

  • Switched to catch2 for testing.
  • Some minor tweaks.

  🛠 Fixed

  • ✂ Removed some undefined behaviour.

• v1.6.8 Changes

  August 15, 2019

  🔄 Changed

  • ⚠ Various code cleanups due to clang-tidy warnings.

  🛠 Fixed

  • Made data_view::compare noexcept.

• v1.6.7 Changes

  February 21, 2018

  🛠 Fixed

  • Signed-unsigned comparison on 32 bit systems.

• v1.6.6 Changes

  February 20, 2018

  🛠 Fixed

  • 🛠 Fixed several place with possible undefined behaviour.

• v1.6.5 Changes

  February 05, 2018

  🛠 Fixed

  • Avoid UB: Do not calculate pointer outside array bounds.
  • Specify proto2 syntax in .proto files to appease protoc.

• v1.6.4 Changes

  November 08, 2018

  ➕ Added

  • ➕ Add function data() to get the not yet read data from a pbf_reader.
  • New add_packed_fixed() template function for pbf_writer.
  • New length_of_varint() helper function calculates how long a varint would be for a specified value.

  🔄 Changed

  • 🆓 More consistent implementation of operators as free friend functions.

  🛠 Fixed

  • 🛠 Fixed some zigzag encoding tests on MSVC.
  • ➕ Add extra cast so we do an xor with unsigned ints.
  • No more bitwise operations on signed integers in varint decoder.
  • No more bitwise operations on signed integers in zigzag encoder/decoder.

• v1.6.3 Changes

  July 17, 2018

  🔄 Changed

  • 🚚 Moved byteswap_inplace functions from detail into protozero namespace. They can be useful outsize protozero.
  • ✅ More asserts and unit tests and small cleanups.

• v1.6.2 Changes

  March 09, 2018

  🔄 Changed

  • ⚡️ Update included catch.hpp to v1.12.0.
  • 🚚 Move basic unit tests into their own directory (test/unit).
  • 👌 Improved clang-tidy config and fixed some code producing warnings.

  🛠 Fixed

  • Buffer overflow in pbf-decoder tool.

• v1.6.1 Changes

  November 16, 2017

  ➕ Added

  • Document internal handling of varints.
  • ➕ Add aliases for fixed iterators, too.

  🔄 Changed

  • 🛠 The const_fixed_iterator is now a random access iterator making code using it potentially more performant (for instance when using std::distance)
  • Overloads std::distance for the varint and svarint iterators. This is better than the workaround with the rage_size function used before.

  🛠 Fixed

  • ✅ Rename .proto files in some tests to be unique. This solves a problem when building with newer versions of the Google Protobuf library.
  • ✅ Floating point comparisons in tests are now always correctly done using Approx().

• v1.6.0 Changes

  October 24, 2017

  ➕ Added

  • Comparison functions (<, <=, >, >=) for data_view. Allows use in std::map for instance.
  • Tool pbf-decoder for decoding raw messages. This has limited use for normal users, but it can be used for fuzzing.

  🔄 Changed

  • 🏗 Protozero now uses CMake to build the tests etc. This does not affect simple users of the library, but if you are using CMake yourself you might want to use the cmake/FindProtozero.cmake module provided. The README contains more information about build options.
  • 🚚 Moved data_view class from types.hpp into its own header file data_view.hpp.
  • 🛠 Implementation of the const_fixed_iterator to use only a single pointer instead of two.
  • Made operator== and operator!= on data_view constexpr.
  • 🗄 The pbf_reader constructor taking a std::pair is deprecated. Use one of the other constructors instead.

  🛠 Fixed

  • Varints where the last byte was larger than what would fit in 64bit were triggering undefined behaviour. This can only happen when the message being decoded was corrupt in some way.
  • Do not assert when reading too long varints for bools any more. A valid encoder should never generate varints with more than one byte for bools, but if they are longer that's not really a problem, so just handle it.
  • 🛠 Throw exception if the length of a packed repeated field of a fixed-length type is invalid. The length must always be a multiple of the size of the underlying type. This can only happen if the data is corrupted in some way, a valid encoder would never generate data like this.
  • 👻 Throw an exception when reading invalid tags. This can only happen if the data is corrupted in some way, a valid encoder would never generate invalid tags.

• 1
• 2
• 3
• Next ›
• Last »