diff options
| author | Jay Berkenbilt <ejb@ql.org> | 2021-12-20 17:34:00 +0100 |
|---|---|---|
| committer | Jay Berkenbilt <ejb@ql.org> | 2021-12-20 17:34:00 +0100 |
| commit | 038dd2d5ee521d41b2d2e71eea96c3858c5b6d4e (patch) | |
| tree | 0fd1a7cd15861f038bee7284671f9d83fd54c378 | |
| parent | 5d26f29eeb8ef338ecf7de23446651a1a3a662d2 (diff) | |
| download | qpdf-038dd2d5ee521d41b2d2e71eea96c3858c5b6d4e.tar.zst | |
Remove uninitialized error idea
QPDFObjectHandle gets copied a lot, so let's not add another field.
For performance reasons, QPDFObjectHandle does not indirect through a
smart pointer, so this would also be an ABI change.
| -rw-r--r-- | TODO | 10 |
1 files changed, 0 insertions, 10 deletions
@@ -11,16 +11,6 @@ Next * Consider creating a qpdf wiki. See also Documentation below. -* For QPDFObjectHandle, provide a way on and after construction - to specify the error message that will be thrown if the - uninitialized object is accessed. Attach this to the trailer or any - other uninitialized object handle that might be returned. Explain in - getTrailer() that we don't explicitly check since the trailer is - only uninitialized when the user doesn't call a process method, and - adding a check for every call will be expensive. Make sure the error - thrown when an uninitialized trailer is accessed provides useful - information. Test from the C API as well as the C++ API. - Documentation ============= |