From c7a4967d10fb9688f235baa8e57a1fb578f5387d Mon Sep 17 00:00:00 2001 From: Jay Berkenbilt Date: Thu, 8 Sep 2022 11:06:15 -0400 Subject: Change reset to disconnect and clarify comments I decided that it's actually fine to copy a direct object to another QPDF. Even if we eventually prevent a QPDFObject from having multiple parents, this could happen if an object is moved. --- libqpdf/QPDFObjectHandle.cc | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'libqpdf/QPDFObjectHandle.cc') diff --git a/libqpdf/QPDFObjectHandle.cc b/libqpdf/QPDFObjectHandle.cc index 556e3a1e..d31af881 100644 --- a/libqpdf/QPDFObjectHandle.cc +++ b/libqpdf/QPDFObjectHandle.cc @@ -249,7 +249,7 @@ QPDFObjectHandle::operator!=(QPDFObjectHandle const& rhs) const } void -QPDFObjectHandle::reset() +QPDFObjectHandle::disconnect() { // Recursively remove association with any QPDF object. This // method may only be called during final destruction. @@ -257,7 +257,7 @@ QPDFObjectHandle::reset() // pointer itself, so we don't do that here. Other objects call it // through this method. if (!isIndirect()) { - this->obj->reset(); + this->obj->disconnect(); } } -- cgit v1.2.3-70-g09d2