ContinueAsynchronously (Daemon subroutine): Difference between revisions
Jump to navigation
Jump to search
mNo edit summary |
m (→Usage notes) |
||
| Line 20: | Line 20: | ||
==Usage notes== | ==Usage notes== | ||
<ul> | <ul> | ||
<li>Issuing | <li>Issuing <var>ContinueAsynchronously</var> against a daemon not in a <var>ReturnToMaster</var> wait results in an <var>[[IncorrectDaemonState class|IncorrectDaemonState]]</var> exception.</li> | ||
<li>The <var>[[Continue (Daemon subroutine)|Continue]]</var> and <var>[[ContinueIndependently (Daemon subroutine)|ContinueIndependently]]</var> methods also tell a daemon to continue from a <var>ReturnToMaster</var>.</li> | <li>The <var>[[Continue (Daemon subroutine)|Continue]]</var> and <var>[[ContinueIndependently (Daemon subroutine)|ContinueIndependently]]</var> methods also tell a daemon to continue from a <var>ReturnToMaster</var> wait.</li> | ||
</ul> | </ul> | ||
Revision as of 00:18, 18 May 2012
Continue processing asynchronously in daemon (Daemon class)
[Introduced in Sirius Mods 8.1]
This page is under construction.
Syntax
daemon:ContinueAsynchronously[( [Input= object])] Throws DaemonLost, IncorrectDaemonState
Syntax terms
| daemon | A previously defined Daemon object. |
|---|---|
| inputObj | This optional, name allowed, argument is either:
|
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.