From e01e07b6e76ad6f571cefe679d112fede88cf1db Mon Sep 17 00:00:00 2001 From: Greg Clayton Date: Thu, 18 Apr 2013 18:10:51 +0000 Subject: Since we use C++11, we should switch over to using std::unique_ptr when C++11 is being used. To do this, we follow what we have done for shared pointers and we define a STD_UNIQUE_PTR macro that can be used and it will "do the right thing". Due to some API differences in std::unique_ptr and due to the fact that we need to be able to compile without C++11, we can't use move semantics so some code needed to change so that it can compile with either C++. Anyone wanting to use a unique_ptr or auto_ptr should now use the "STD_UNIQUE_PTR(TYPE)" macro. llvm-svn: 179779 --- lldb/scripts/Python/python-wrapper.swig | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'lldb/scripts/Python/python-wrapper.swig') diff --git a/lldb/scripts/Python/python-wrapper.swig b/lldb/scripts/Python/python-wrapper.swig index 2189193cfbb..9834f0f2b63 100644 --- a/lldb/scripts/Python/python-wrapper.swig +++ b/lldb/scripts/Python/python-wrapper.swig @@ -652,11 +652,11 @@ LLDBSWIGPython_CastPyObjectToSBValue return sb_ptr; } -// Currently, SBCommandReturnObjectReleaser wraps an std::auto_ptr to an +// Currently, SBCommandReturnObjectReleaser wraps a unique pointer to an // lldb_private::CommandReturnObject. This means that the destructor for the // SB object will deallocate its contained CommandReturnObject. Because that // object is used as the real return object for Python-based commands, we want -// it to stay around. Thus, we release the auto_ptr before returning from +// it to stay around. Thus, we release the unique pointer before returning from // LLDBSwigPythonCallCommand, and to guarantee that the release will occur no // matter how we exit from the function, we have a releaser object whose // destructor does the right thing for us -- cgit v1.2.3