ContinueAsynchronously (Daemon subroutine): Difference between revisions
Jump to navigation
Jump to search
mNo edit summary |
m (→Syntax terms) |
||
Line 10: | Line 10: | ||
<tr><th>daemon</th> | <tr><th>daemon</th> | ||
<td>A previously defined <var>Daemon</var> object. </td></tr> | <td>A previously defined <var>Daemon</var> object. </td></tr> | ||
<tr><th> | <tr><th>object</th> | ||
<td>This optional, [[Notation conventions for methods#Named parameters|name allowed]], argument is either: | <td>This optional, [[Notation conventions for methods#Named parameters|name allowed]], argument is either: | ||
<ul> | <ul> |
Revision as of 16:13, 31 May 2012
Continue processing asynchronously in daemon (Daemon class)
[Introduced in Sirius Mods 8.1]
This method tells a daemon that issued a Daemon class ReturnToMaster call to continue processing at the point of the call. Unlike the Continue method, ContinueAsynchronously returns immediately, thus allowing the thread that issued ContinueAsynchronously to run in parallel with the daemon thread.
Syntax
daemon:ContinueAsynchronously[( [Input= object])] Throws DaemonLost, IncorrectDaemonState
Syntax terms
daemon | A previously defined Daemon object. |
---|---|
object | This optional, name allowed, argument is either:
|
Exceptions
This subroutine can throw the following exceptions:
- IncorrectDaemonState
- If the daemon thread is not in a ReturnToMaster wait when ContinueAsynchronously is issued, an IncorrectDaemonState exception is thrown. This exception will only be thrown in Sirius Mods version 8.1 and later.
Usage notes
- The Continue and ContinueIndependently methods also tell a daemon to continue from a ReturnToMaster wait.