Amebis/wxWidgets
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

warn the user about using getters of objects in invalid state

Browse Source 
git-svn-id: https://svn.wxwidgets.org/svn/wx/wxWidgets/trunk@52653 c3d73ce0-8a6f-49c7-b76d-6d57e0e08775
This commit is contained in:
Francesco Montorsi
2008-03-21 18:04:00 +00:00
parent 106ef548fd
commit f0a9a84c09
1 changed files with 6 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

7
docs/doxygen/overviews/refcount.h
View File

@@ -53,7 +53,7 @@ provide comparison operators.
Also note that if you only need to do a @c shallow comparison between two Also note that if you only need to do a @c shallow comparison between two
wxObject derived classes, you should not use the == and != operators but wxObject derived classes, you should not use the == and != operators but
rather the wxObject::IsSameAs function. rather the wxObject::IsSameAs() function.
@section overview_refcount_destruct Object Destruction @section overview_refcount_destruct Object Destruction
@@ -90,6 +90,11 @@ operators and copy constructors since they are reference-counted:
Note that the list above reports the objects which are reference counted in all Note that the list above reports the objects which are reference counted in all
ports of wxWidgets; some ports may use this technique also for other classes. ports of wxWidgets; some ports may use this technique also for other classes.
All the objects implement a function IsOk() to test if they are referencing valid
data; when the objects are in uninitialized state, you can only use the IsOk() getter;
trying to call any other getter, e.g. wxBrush::GetStyle() on the ::wxNullBrush object,
will result in an assert failure in debug builds.
@section overview_refcount_object Making Your Own Reference Counted Class @section overview_refcount_object Making Your Own Reference Counted Class