X-Git-Url: https://git.saurik.com/wxWidgets.git/blobdiff_plain/880efa2a137ce3e3f39236d0dc85f5d2dacdda12..906c935a80b10d53cecf57f71ab5f3f4f1d529ec:/docs/doxygen/overviews/runtimeclass.h diff --git a/docs/doxygen/overviews/runtimeclass.h b/docs/doxygen/overviews/runtimeclass.h index b2bf4524b0..6f6638dc6c 100644 --- a/docs/doxygen/overviews/runtimeclass.h +++ b/docs/doxygen/overviews/runtimeclass.h @@ -3,7 +3,7 @@ // Purpose: topic overview // Author: wxWidgets team // RCS-ID: $Id$ -// Licence: wxWindows license +// Licence: wxWindows licence ///////////////////////////////////////////////////////////////////////////// /** @@ -14,7 +14,7 @@ @li @ref overview_rtti_classinfo @li @ref overview_rtti_example -@seealso +@see @li wxObject @li wxClassInfo @@ -35,7 +35,7 @@ Most C++ GUI frameworks overcome these limitations by means of a set of macros and functions and wxWidgets is no exception. As it originated before the addition of RTTI to the C++ standard and as support for it is still missing from some (albeit old) compilers, wxWidgets doesn't (yet) use it, but provides -it's own macro-based RTTI system. +its own macro-based RTTI system. In the future, the standard C++ RTTI will be used though and you're encouraged to use whenever possible the wxDynamicCast macro which, for the implementations @@ -79,7 +79,7 @@ This class stores meta-information about classes. An application may use macros such as DECLARE_DYNAMIC_CLASS and IMPLEMENT_DYNAMIC_CLASS to record runtime information about a class, including: -@li It's position in the inheritance hierarchy. +@li Its position in the inheritance hierarchy. @li The base class name(s) (up to two base classes are permitted). @li A string representation of the class name. @li A function that can be called to construct an instance of this class. @@ -93,7 +93,7 @@ You can get the wxClassInfo for a class by using the CLASSINFO macro, e.g. CLASSINFO(wxFrame). You can get the wxClassInfo for an object using wxObject::GetClassInfo. -@seealso +@see @li wxObject @li wxCreateDynamicObject