slower: it is $O(log(N))$ instead of constant time (neglecting time spent in
memory allocation routine). However, in a usual situation elements are added to
an array much less often than searched inside it, so wxSortedArray may lead to
-huge performance improvements compared to wxArray. As wxArray this array can not
-be used
+huge performance improvements compared to wxArray. Finally, it should be
+noticed that, as wxArray, wxSortedArray can not be used to store anything of
+sizeof() larger than max(sizeof(long), sizeof(void *)) - an assertion failure
+will be raised from the constructor otherwise.
wxObjArray class treats its elements like "objects". It may delete them when
they are removed from the array (invoking the correct destructor) and copies
This macro declares a new object array class named {\it name} and containing
the elements of type {\it T}. Example:
+
\begin{verbatim}
class MyClass;
WX_DEFINE_OBJARRAY(MyClass, wxArrayOfMyClass); // note: not "MyClass *"!
\end{verbatim}
+
You must use \helpref{WX\_DEFINE\_OBJARRAY()}{wxdefineobjarray} macro to define
the array class - otherwise you would get link errors.
It can not be used with wxObjArrays - but they will delete their elements anyhow
when you call Empty().
-\membersection{Default constructors}\label{wxarrayctor}
+\membersection{Default constructors}\label{wxarrayctordef}
\func{}{wxArray}{}
should return a negative, zero or positive value according to whether the first
element passed to it is less than, equal to or greater than the second one.
-\membersection{wxArray copy constructor and assignemnt operator}\label{wxarrayctorcopy}
+\membersection{wxArray copy constructor and assignment operator}\label{wxarrayctorcopy}
\func{}{wxArray}{\param{const wxArray\& }{array}}