|
|
@@ -1698,7 +1698,7 @@ its siblings, it can create *messages* which can be injected into the event queu
|
|
|
Notice the change of terminology, where *message* indicates that the entry
|
|
|
was created by code procesing, rather than an interrupt.
|
|
|
|
|
|
-### PostMessage
|
|
|
+### PostMessage()
|
|
|
|
|
|
We need a service routine to add messages to the event queue:
|
|
|
`postMessage()`. This call is very smimilar `newEvent()` which should
|
|
|
@@ -1720,7 +1720,7 @@ reason that I use different names is that some more sophisticated operating
|
|
|
systems require that these two functions are *not* identical.
|
|
|
</details>
|
|
|
|
|
|
-### SendMessage
|
|
|
+### SendMessage()
|
|
|
|
|
|
In some cases we may want the sibling task to process the information immediately.
|
|
|
This means:
|
