ContinueAsynchronously (Daemon subroutine): Difference between revisions
Jump to navigation
Jump to search
mNo edit summary |
m (→Syntax terms) |
||
Line 17: | Line 17: | ||
</ul> | </ul> | ||
</table> | </table> | ||
==Exceptions== | |||
This subroutine can throw the following exceptions: | |||
<dl> | |||
<dt><var>[[IncorrectDaemonState class|IncorrectDaemonState]]</var> | |||
<dd>If the daemon thread is not in the appropriate state, an <var>IncorrectDaemonState</var> exception is thrown. This exception will only be thrown in <var class="product">Sirius Mods</var> version 8.1 and later. | |||
</dl> | |||
==Usage notes== | ==Usage notes== |
Revision as of 15:37, 30 May 2012
Continue processing asynchronously in daemon (Daemon class)
[Introduced in Sirius Mods 8.1]
This method tells a daemon that did a ReturnToMaster Daemon class 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. |
---|---|
inputObj | This optional, name allowed, argument is either:
|
Exceptions
This subroutine can throw the following exceptions:
- IncorrectDaemonState
- If the daemon thread is not in the appropriate state, an IncorrectDaemonState exception is thrown. This exception will only be thrown in Sirius Mods version 8.1 and later.
Usage notes
- Issuing ContinueAsynchronously against a daemon not in a ReturnToMaster wait results in an IncorrectDaemonState exception.
- The Continue and ContinueIndependently methods also tell a daemon to continue from a ReturnToMaster wait.