[fdo-users] Re: Memory management and FdoPtr
gavin.cramer at autodesk.com
Mon May 14 17:00:33 EDT 2012
If the caller is using FdoPtr, it can just let that pointer fall out of scope (or reassign it if it's in a loop).
FDO_SAFE_RELEASE is for callers that use a plain pointer, not a smart pointer.
From: fdo-users-bounces at lists.osgeo.org [mailto:fdo-users-bounces at lists.osgeo.org] On Behalf Of Jackie Ng
Sent: Saturday, May 12, 2012 2:50 PM
To: fdo-users at lists.osgeo.org
Subject: [fdo-users] Re: Memory management and FdoPtr
That is correct. The onus is always on the method caller to release via
FDO_SAFE_RELEASE or automatically via FdoPtr
View this message in context: http://osgeo-org.1560.n6.nabble.com/Memory-management-and-FdoPtr-tp4968699p4973896.html
Sent from the FDO Users mailing list archive at Nabble.com.
fdo-users mailing list
fdo-users at lists.osgeo.org
More information about the fdo-users