All Versions
26
Latest Version
Avg Release Cycle
93 days
Latest Release
261 days ago
Changelog History
Page 1
Changelog History
Page 1
-
v1.7.0
June 08, 2020โ Added
- ๐ Support for buffer types other that
std::string
.pbf_writer
is now just a typedef forbasic_pbf_writer<std::string>
. Other buffer types can be used withbasic_pbf_writer
. Seedoc/advanced.md
for details.
๐ Changed
- Switched to catch2 for testing.
- Some minor tweaks.
๐ Fixed
- โ Removed some undefined behaviour.
- ๐ Support for buffer types other that
-
v1.6.8
August 15, 2019๐ Changed
- โ Various code cleanups due to clang-tidy warnings.
๐ Fixed
- Made
data_view::compare
noexcept.
-
v1.6.7
February 21, 2018๐ Fixed
- Signed-unsigned comparison on 32 bit systems.
-
v1.6.6
February 20, 2018๐ Fixed
- ๐ Fixed several place with possible undefined behaviour.
-
v1.6.5
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
November 08, 2018โ Added
- โ Add function
data()
to get the not yet read data from apbf_reader
. - New
add_packed_fixed()
template function forpbf_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.
- โ Add function
-
v1.6.3
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.
- ๐ Moved
-
v1.6.2
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
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 usingstd::distance
) - Overloads
std::distance
for the varint and svarint iterators. This is better than the workaround with therage_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
October 24, 2017โ Added
- Comparison functions (<, <=, >, >=) for
data_view
. Allows use instd::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 fromtypes.hpp
into its own header filedata_view.hpp
. - ๐ Implementation of the
const_fixed_iterator
to use only a single pointer instead of two. - Made
operator==
andoperator!=
ondata_view
constexpr. - ๐ The
pbf_reader
constructor taking astd::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.
- Comparison functions (<, <=, >, >=) for