documents/userman/umsexcept.tex

6 % in compliance with the License.  You may obtain a copy of the License
47     \item the handler can interact with the interrupted execution only via
66 %    \item the handler cannot interact with interrupted execution, except via
104     <code to deal with Event>
118 An anonymous event is created with the built-in
131 is raised, a copy of the handler goal with fresh variables will be executed).
149 \bipref{event/1}{../bips/kernel/event/event-1.html} with the event
233 This finds and cancels all pending after events with name \about{EventId} and
244 multiple times with multiple calls to \predspec{event_after/2} and
279 The following is an example of waking a goal with a timed event.
306 \subsection{Aborting an Execution with Events}
320 When dealing with events that occur asynchronously (in particular after-events),
324 declared with the defer-property, which means that all further event handling
334         <deal with event>,
416 with the
418 \pattern{Name/Arity}, and \about{HomeModule} will be unified with the module
432 To enable the user to conveniently write predicates with error checking
443 with the culprit \about{Goal}.
478 should be used with caution. The action of an error handler could have side
483 %a particular error handler may interact with
614 %when a file with this declaration is being compiled,
774     Invoke \predspec{throw/1} with the interupt's symbolic name.
806 %with the debugger in leap mode, in creep mode or without debugger respectively.
807 %The flags can be set with the built-in
809 %and queried with
846 %such that {\it TagExit} unifies with the {\it Tag} of a
853 %If {\it Tag} does not unify with {\it TagExit}, the system continues
857 %not unify with a {\it Tag}  of any uncompleted call of
862 %Since {\eclipse} provides the user with a sophisticated exception