qpdf - qpdf + zopfli patch

Age	Commit message (Collapse)	Author
2023-05-21	Rerun clang-format	Jay Berkenbilt

2023-05-20	Rerun format_code (after merging clang-tidy PR)	Jay Berkenbilt

2023-05-20	Use auto when initializing with a cast	m-holger

2023-05-20	Replace deprecated C++ includes	m-holger

2022-11-25	Code formatting updates	Jay Berkenbilt

2022-05-04	Make assert handling less error-prone	Jay Berkenbilt
	Prevent my future self or other contributors from using assert in tests and then having that assert not do anything because of the NDEBUG macro.
2022-04-04	Programmatically apply new formatting to code	Jay Berkenbilt
	Run this: for i in */.cc */.c */.h */.hh; do clang-format < $i >\| $i.new && mv $i.new $i done
2022-03-07	Force assert to be defined in test code	Jay Berkenbilt

2021-11-04	Add QIntC::range_check_subtract	Jay Berkenbilt

2020-11-21	Handle negative numbers in QIntC::range_check (fuzz issue 26994)	Jay Berkenbilt

2019-09-17	Don't assume char is signed in int conversion tests (fixes #361)	Jay Berkenbilt

2019-08-31	spell check	Jay Berkenbilt

2019-06-21	Fix sign and conversion warnings (major)	Jay Berkenbilt
	This makes all integer type conversions that have potential data loss explicit with calls that do range checks and raise an exception. After this commit, qpdf builds with no warnings when -Wsign-conversion -Wconversion is used with gcc or clang or when -W3 -Wd4800 is used with MSVC. This significantly reduces the likelihood of potential crashes from bogus integer values. There are some parts of the code that take int when they should take size_t or an offset. Such places would make qpdf not support files with more than 2^31 of something that usually wouldn't be so large. In the event that such a file shows up and is valid, at least qpdf would raise an error in the right spot so the issue could be legitimately addressed rather than failing in some weird way because of a silent overflow condition.
2019-06-21	New safe type converters in QIntC	Jay Berkenbilt