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.
-----Original Message-----
From:
[hidden email] [mailto:
[hidden email]] On Behalf Of Jackie Ng
Sent: Saturday, May 12, 2012 2:50 PM
To:
[hidden email]
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
- Jackie
--
View this message in context:
http://osgeo-org.1560.n6.nabble.com/Memory-management-and-FdoPtr-tp4968699p4973896.htmlSent from the FDO Users mailing list archive at Nabble.com.
_______________________________________________
fdo-users mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/fdo-users_______________________________________________
fdo-users mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/fdo-users