X-Git-Url: https://git.saurik.com/wxWidgets.git/blobdiff_plain/233f573883834b6c86ad5a9d72fdb6a260f74f81..5ecd98f17596ce1593741fb379e1ef813de41fcc:/include/wx/osx/core/cfref.h diff --git a/include/wx/osx/core/cfref.h b/include/wx/osx/core/cfref.h index 90c7ae4158..c4a6b3c17a 100644 --- a/include/wx/osx/core/cfref.h +++ b/include/wx/osx/core/cfref.h @@ -4,7 +4,6 @@ // Author: David Elliott // Modified by: Stefan Csomor // Created: 2007/05/10 -// RCS-ID: $Id$ // Copyright: (c) 2007 David Elliott , Stefan Csomor // Licence: wxWindows licence // Notes: See http://developer.apple.com/documentation/CoreFoundation/Conceptual/CFMemoryMgmt/index.html @@ -172,7 +171,7 @@ public: @param p The raw pointer to assume ownership of. May be NULL. @discussion Like shared_ptr, it is assumed that the caller has a strong reference to p and intends to transfer ownership of that reference to this ref holder. If the object comes from - a Create or Copy method then this is the correct behavior. If the object comes from + a Create or Copy method then this is the correct behaviour. If the object comes from a Get method then you must CFRetain it yourself before passing it to this constructor. A handy way to do this is to use the non-member wxCFRefFromGet factory funcion. This method is templated and takes an otherType *p. This prevents implicit conversion @@ -364,7 +363,7 @@ inline wxCFWeakRef static_cfref_cast(const wxCFRef &other } /*! @function CFRelease - @abstract Overloads CFRelease so that the user is warned of bad behavior. + @abstract Overloads CFRelease so that the user is warned of bad behaviour. @discussion It is rarely appropriate to retain or release a wxCFRef. If one absolutely must do it he can explicitly get() the raw pointer Normally, this function is unimplemented resulting in a linker error if used. @@ -373,7 +372,7 @@ template inline void CFRelease(const wxCFRef & cfref) DEPRECATED_ATTRIBUTE; /*! @function CFRetain - @abstract Overloads CFRetain so that the user is warned of bad behavior. + @abstract Overloads CFRetain so that the user is warned of bad behaviour. @discussion It is rarely appropriate to retain or release a wxCFRef. If one absolutely must do it he can explicitly get() the raw pointer Normally, this function is unimplemented resulting in a linker error if used.