| Age | Commit message (Collapse) | Author |
|---|
|
Part of #729
|
|
Part of #729
|
|
Part of #729
|
|
Also, inline method and add optional parameter error_msg.
|
|
Code tidy: remove redundant calls to smart_ptrs get() method
|
|
|
|
Also, make QPDFObjectHandle::isIndirect const.
|
|
Code tidy : replace 0 with nullptr or true
|
|
|
|
Remove any ambiguity around whether old or new value is being
returned.
|
|
Use 'QPDFObjGen const&' instead of 'int, int' in signature.
|
|
Change method signatures to use QPDFObjGen.
Replace QPDF_Stream::objid and generation with QPDF_Stream::og.
|
|
Change method signatures to use QPDFObjGen.
Use QPDFObjGen methods where possible.
Remove redundant QPDF::objGenToIndirect.
|
|
Change method signature to use QPDFObjGen.
|
|
|
|
Also, revert inlining of unparse and operator << from commit 4c6640c in
order to avoid exposing QUtil.
|
|
|
|
Move responsibility for creating shared pointers to objects and cloning from QPDFObjectHandle to QPDFObject.
|
|
|
|
|
|
Also, use methods to access objid and generation.
|
|
When there is no context for writing output or error messages, use the
default logger.
|
|
Remove variables obsoleted by commit 4f24617.
|
|
|
|
I decided these were confusing and inconsistent with how JSON works.
They muddle the API rather than improving it.
|
|
|
|
When an empty string was passed to replaceStreamData, the code was
passing a null pointer to memcpy. Since a 0 size was also passed, this
was harmless, but it triggers sanitizer errors. The code properly
handles a null pointer as the buffer in other places.
|
|
|
|
Not fully exercised in this commit
|
|
Update getJSON() methods and calls to them
|
|
|
|
|
|
This reverts commit dc059560e73e0b373a6e54e71b07e3af4b692cb4.
I changed my mind. There's no harm in leaving it deprecated for a
release cycle.
|
|
See ChangeLog for rationale for not deprecating it as originally
planned.
|
|
Where not possible, use "auto" to get the iterator type.
Editorial note: I have avoid this change for a long time because of
not wanting to make gratuitous changes to version history, which can
obscure when certain changes were made, but with having recently
touched every single file to apply automatic code formatting and with
making several broad changes to the API, I decided it was time to take
the plunge and get rid of the older (pre-C++11) verbose iterator
syntax. The new code is just easier to read and understand, and in
many cases, it will be more effecient as fewer temporary copies are
being made.
m-holger, if you're reading, you can see that I've finally come
around. :-)
|
|
Change .clang-format and commit automated changes from a fresh run of
format-code
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
* Merge overloaded functions by adding default values
* Remove non-const methods that are identical to const methods
|
|
(patrepl and cleanpatch are my own utilities)
patrepl s/PointerHolder/std::shared_ptr/g {include,libqpdf}/qpdf/*.hh
patrepl s/PointerHolder/std::shared_ptr/g libqpdf/*.cc
patrepl s/make_pointer_holder/std::make_shared/g libqpdf/*.cc
patrepl s/make_array_pointer_holder/QUtil::make_shared_array/g libqpdf/*.cc
patrepl s,qpdf/std::shared_ptr,qpdf/PointerHolder, **/*.cc **/*.hh
git restore include/qpdf/PointerHolder.hh
cleanpatch
./format-code
|
|
Add comments to force line breaks, parenthesize function arguments
that are contatenated strings, etc. -- these kinds of changes improve
clang-format's results and also cause emacs cc-mode to match
clang-format. After this type of change, most of the time, when
clang-format and emacs disagree, clang-format is better.
|
|
Run this:
for i in **/*.cc **/*.c **/*.h **/*.hh; do
clang-format < $i >| $i.new && mv $i.new $i
done
|
|
Remove test for type == /XObject in QPDFObjectHandle::isFormXObject
as type value is optional (as per spec 8.10.2).
Replace code to test for /Form in QPDFJob::shouldRemoveUnreferencedResources
with a call to isFormXObject.
|
|
This comment expands all tabs using an 8-character tab-width. You
should ignore this commit when using git blame or use git blame -w.
In the early days, I used to use tabs where possible for indentation,
since emacs did this automatically. In recent years, I have switched
to only using spaces, which means qpdf source code has been a mixture
of spaces and tabs. I have avoided cleaning this up because of not
wanting gratuitous whitespaces change to cloud the output of git
blame, but I changed my mind after discussing with users who view qpdf
source code in editors/IDEs that have other tab widths by default and
in light of the fact that I am planning to start applying automatic
code formatting soon.
|
|
|
