qpdf/libqpdf/QPDFObject.cc

#include <qpdf/QPDFObject_private.hh>

#include <qpdf/QPDF.hh>
#include <qpdf/QPDF_Destroyed.hh>

void
QPDFObject::destroy()
{
    value = QPDF_Destroyed::getInstance();
}
Rename QPDFValueProxy.hh and QPDFValueProxy.cc Preparing to change the class name back to QPDFObject 2022-09-08 11:12:10 -04:00			`#include <qpdf/QPDFObject_private.hh>`
Add method QPDFObject::resolve 2022-08-14 10:50:30 +01:00
			`#include <qpdf/QPDF.hh>`
Create a special "destroyed" type rather than using null When a QPDF is destroyed, changing indirect objects to direct nulls makes them effectively disappear silently when they sneak into other places. Instead, we should treat this as an error. Adding a destroyed object type makes this possible. 2022-09-08 08:03:57 -04:00			`#include <qpdf/QPDF_Destroyed.hh>`
Add method QPDFObject::resolve 2022-08-14 10:50:30 +01:00
Create a special "destroyed" type rather than using null When a QPDF is destroyed, changing indirect objects to direct nulls makes them effectively disappear silently when they sneak into other places. Instead, we should treat this as an error. Adding a destroyed object type makes this possible. 2022-09-08 08:03:57 -04:00			`void`
Rename QPDFValueProxy back to QPDFObject QPDFValueProxy wasn't a good name for it. We decided the evil of having the header file be named QPDFObject_private.hh was less than the evil of having the class be named something other than what it should have been named. 2022-09-08 11:29:23 -04:00			`QPDFObject::destroy()`
Create a special "destroyed" type rather than using null When a QPDF is destroyed, changing indirect objects to direct nulls makes them effectively disappear silently when they sneak into other places. Instead, we should treat this as an error. Adding a destroyed object type makes this possible. 2022-09-08 08:03:57 -04:00			`{`
			`value = QPDF_Destroyed::getInstance();`
			`}`