Recent changes to Events

Events modified by Will Pittenger

Will Pittenger — Sun, 16 Feb 2014 10:28:03 -0000

--- v4
+++ v5
@@ -24,3 +24,5 @@
 :::text
 MyCommandEvent 3
 ~~~~
+
+Please note that with [Delegates], you are declaring a type.  With events, you're declaring an instance of the event.

Events modified by Will Pittenger

Will Pittenger — Sun, 16 Feb 2014 10:27:18 -0000

--- v3
+++ v4
@@ -1,6 +1,7 @@
 Like with .NET, ASIL events are based on [Delegates].  Declaring your **[event](keywords-event)** is simple.

 ~~~~
+:::text
 delegate command MyDelegateCommand var int i

 event MyDelegateCommand MyCommandEvent
@@ -9,6 +10,7 @@
 When it's time to subscribe, first declare a matching procedure, here a **[command](keywords-command)**, and then use the **[++](operator-inc)** operator.  To unsubscribe, use the **[--](operator-dec)** operator.  As you may recall, we use the **[&](operator-amp)** **[operator](keywords-operator)** to obtain a delegate instance from a procedure name.

 ~~~~
+:::text
 command MatchingCommand var int i
   ' Have the command do soemething

@@ -19,5 +21,6 @@
 Now lets trigger the **[event](keywords-event)**.  Events are really arrays of delegates derived from EventType.  ASIL adds code to call each **[delegate](keywords-delegate)** in the array.  If the array is empty, nothing happens.

 ~~~~
+:::text
 MyCommandEvent 3
 ~~~~

Events modified by Will Pittenger

Will Pittenger — Fri, 14 Feb 2014 04:48:37 -0000

--- v2
+++ v3
@@ -1,4 +1,4 @@
-Like with .NET, ASIL events are based on [Delegates].  Declaring your [**event**] is simple.
+Like with .NET, ASIL events are based on [Delegates].  Declaring your **[event](keywords-event)** is simple.

 ~~~~
 delegate command MyDelegateCommand var int i
@@ -6,7 +6,7 @@
 event MyDelegateCommand MyCommandEvent
 ~~~~

-When it's time to subscribe, first declare a matching procedure, here a [**command**], and then use the [**++**] operator.  To unsubscribe, use the [**--**] operator.  As you may recall, we use the [**&**] [**operator**] to obtain a delegate instance from a procedure name.
+When it's time to subscribe, first declare a matching procedure, here a **[command](keywords-command)**, and then use the **[++](operator-inc)** operator.  To unsubscribe, use the **[--](operator-dec)** operator.  As you may recall, we use the **[&](operator-amp)** **[operator](keywords-operator)** to obtain a delegate instance from a procedure name.

 ~~~~
 command MatchingCommand var int i
@@ -16,7 +16,7 @@
 MyCommandEvent -- &MatchingCommand ' unsubscribe
 ~~~~

-Now lets trigger the [**event**].  Events are really arrays of delegates derived from EventType.  ASIL adds code to call each [**delegate**] in the array.  If the array is empty, nothing happens.
+Now lets trigger the **[event](keywords-event)**.  Events are really arrays of delegates derived from EventType.  ASIL adds code to call each **[delegate](keywords-delegate)** in the array.  If the array is empty, nothing happens.

 ~~~~
 MyCommandEvent 3

Events modified by Will Pittenger

Will Pittenger — Sat, 08 Feb 2014 14:18:03 -0000

--- v1
+++ v2
@@ -1,4 +1,4 @@
-Like with .NET, ASIL events are based on [Delegates].  Declaring your event is simple.
+Like with .NET, ASIL events are based on [Delegates].  Declaring your [**event**] is simple.

 ~~~~
 delegate command MyDelegateCommand var int i
@@ -6,7 +6,7 @@
 event MyDelegateCommand MyCommandEvent
 ~~~~

-When it's time to subscribe, first declare a matching procedure, here a command, and then use the ++ operator.  To unsubscribe, use the -- operator.  As you may recall, we use the & operator to obtain a delegate instance from a procedure name.
+When it's time to subscribe, first declare a matching procedure, here a [**command**], and then use the [**++**] operator.  To unsubscribe, use the [**--**] operator.  As you may recall, we use the [**&**] [**operator**] to obtain a delegate instance from a procedure name.

 ~~~~
 command MatchingCommand var int i
@@ -16,7 +16,7 @@
 MyCommandEvent -- &MatchingCommand ' unsubscribe
 ~~~~

-Now lets trigger the event.  Events are really arrays of delegates derived from EventType.  ASIL adds code to call each delegate in the array.  If the array is empty, nothing happens.
+Now lets trigger the [**event**].  Events are really arrays of delegates derived from EventType.  ASIL adds code to call each [**delegate**] in the array.  If the array is empty, nothing happens.

 ~~~~
 MyCommandEvent 3

Events modified by Will Pittenger

Will Pittenger — Sat, 08 Feb 2014 09:30:21 -0000

Like with .NET, ASIL events are based on [Delegates]. Declaring your event is simple.

delegate command MyDelegateCommand var int i

event MyDelegateCommand MyCommandEvent

When it's time to subscribe, first declare a matching procedure, here a command, and then use the ++ operator. To unsubscribe, use the -- operator. As you may recall, we use the & operator to obtain a delegate instance from a procedure name.

command MatchingCommand var int i
  ' Have the command do soemething

MyCommandEvent ++ &MatchingCommand ' subscribe
MyCommandEvent -- &MatchingCommand ' unsubscribe

Now lets trigger the event. Events are really arrays of delegates derived from EventType. ASIL adds code to call each delegate in the array. If the array is empty, nothing happens.

MyCommandEvent 3