Lines Matching refs:to
18 modern C++ libraries are. For instance, the library doesn't throw exceptions to
19 signal about the errors. Moreover, up to (and including) the version 2.4 of
25 still doesn't use the exceptions by itself but it should be now safe to use the
26 exceptions in the user code and the library tries to help you with this. Please
34 any exceptions by itself and so you don't have to worry about exceptions at all
36 may be not the best one to deal with all possible errors.
38 Another strategy is to use exceptions only to signal truly fatal errors. In
39 this case you probably don't expect to recover from them and the default
40 behaviour -- to simply terminate the program -- may be appropriate. If it is
42 in your wxApp-derived class to perform any clean up tasks. Note, however, that
46 allow you to catch any exceptions generated during the execution of the main
51 Finally, you may also want to continue running even when certain exceptions
56 the \helpref{wxApp::HandleEvent()}{wxapphandleevent} which allows you to handle
62 To use any kind of exception support in the library you need to build it with
63 \texttt{wxUSE\_EXCEPTIONS} set to $1$. This should be the case by default but
68 On the other hand, if you do \emph{not} plan to use exceptions, setting this
69 flag to $0$ or using \texttt{--disable-exceptions} could result in a leaner and
73 showing how to use it. Please look at its sources for further information.