diff options
author | Jay Berkenbilt <ejb@ql.org> | 2012-07-21 15:00:06 +0200 |
---|---|---|
committer | Jay Berkenbilt <ejb@ql.org> | 2012-07-21 15:06:10 +0200 |
commit | 6bbea4baa0c06b39b1b71f1aa6fc276789296556 (patch) | |
tree | 62198136a609c86029d124323be9e2ea72f88d9a /TODO | |
parent | f3e267fce28c58039789379ba3488ad12c20a7f6 (diff) | |
download | qpdf-6bbea4baa0c06b39b1b71f1aa6fc276789296556.tar.zst |
Implement QPDFObjectHandle::parse
Move object parsing code from QPDF to QPDFObjectHandle and
parameterize the parts of it that are specific to a QPDF object.
Provide a version that can't handle indirect objects and that can be
called on an arbitrary string.
A side effect of this change is that the offset used when reporting
invalid stream length has changed, but since the new value seems like
a better value than the old one, the test suite has been updated
rather than making the code backward compatible. This only effects
the offset reported for invalid streams that lack /Length or have an
invalid /Length key.
Updated some test code and exmaples to use QPDFObjectHandle::parse.
Supporting changes include adding a BufferInputSource constructor that
takes a string.
Diffstat (limited to 'TODO')
-rw-r--r-- | TODO | 6 |
1 files changed, 2 insertions, 4 deletions
@@ -20,16 +20,14 @@ Next * Make sure that the release notes call attention to the one API breaking change: removal of length from replaceStreamData. - * Add a way to create new QPDFObjectHandles with a string - representation of them, such as - QPDFObjectHandle::parse("<< /a 1 /b 2 >>"); - * Document thread safety: One individual QPDF or QPDFWriter object can only be used by one thread at a time, but multiple threads can simultaneously use separate objects. * Write some documentation about the design of copyForeignObject. + * Mention QPDFObjectHandle::parse in the documentation. + * copyForeignObject still to do: - qpdf command |