[BACK]Return to mpd52.html CVS log [TXT] [DIR] Up to [ELWIX - Embedded LightWeight unIX -] / embedaddon / mpd / doc

Annotation of embedaddon/mpd/doc/mpd52.html, revision 1.1.1.1

1.1       misho       1: <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
                      2: <HTML>
                      3: <HEAD>
                      4: <META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
                      5: <TITLE>Events</TITLE>
                      6: </HEAD>
                      7: <BODY text="#000000" bgcolor="#ffffff">
                      8: 
                      9: <A HREF="mpd.html"><EM>Mpd 5.6 User Manual</EM></A>
                     10:  <b>:</b> <A HREF="mpd50.html"><EM>Chat Scripting</EM></A>
                     11:  <b>:</b> <EM>Events</EM><BR>
                     12: <b>Previous:</b> <A HREF="mpd51.html"><EM>Script file format and execution</EM></A><BR>
                     13: <b>Next:</b> <A HREF="mpd53.html"><EM>Timer events</EM></A>
                     14: 
                     15: 
                     16: <HR NOSHADE>
                     17:   <H2><A NAME="52"></A>6.2. Events</H2>
                     18: <p>An <b>event</b> is either the expiration of a timer, or the matching
                     19: of some pattern in the input.  Events that haven't happened yet are
                     20: <b>pending events</b>. Pending events are created with the
                     21: <code>timer</code> and <code>match</code> commands, respectively.</p>
                     22: <p>Each pending event has an associated label (called the <b>target
                     23: label</b>) of the event. When and if the event occurs, execution
                     24: resumes starting at the target label. Events only occur during
                     25: the execution of a <code>wait</code> command.</p>
                     26: <p>Events are grouped into named <b>sets</b>. Events in the same
                     27: set are usually related, in the sense that they represent alternate
                     28: outcomes to the same situation.</p>
                     29: <p>A set of pending events may be explicitly <b>cancelled</b>
                     30: (i.e., forgotten) before they occur with the <b><code>cancel</code></b>
                     31: command. All events in the set are cancelled.</p>
                     32: <p>The other way a set of pending events may be cancelled is
                     33: implicitly, when any event in the set occurs. Execution resumes
                     34: at the target label associated with the event that occurred, and
                     35: all other events in that set are immediately cancelled.</p>
                     36: 
                     37: <H3>6.2.1. <A HREF="mpd53.html#53">Timer events</A></H3>
                     38: <H3>6.2.2. <A HREF="mpd54.html#54">Match events</A></H3>
                     39:  <HR NOSHADE>
                     40: <A HREF="mpd.html"><EM>Mpd 5.6 User Manual</EM></A>
                     41:  <b>:</b> <A HREF="mpd50.html"><EM>Chat Scripting</EM></A>
                     42:  <b>:</b> <EM>Events</EM><BR>
                     43: <b>Previous:</b> <A HREF="mpd51.html"><EM>Script file format and execution</EM></A><BR>
                     44: <b>Next:</b> <A HREF="mpd53.html"><EM>Timer events</EM></A>
                     45: 
                     46: 
                     47: 
                     48: </BODY>
                     49: </HTML>
FreeBSD-CVSweb <freebsd-cvsweb@FreeBSD.org>