ContinueAsynchronously (Daemon subroutine): Difference between revisions

From m204wiki
Jump to navigation Jump to search
Line 11: Line 11:
<td>A previously defined <var>Daemon</var> object. </td></tr>
<td>A previously defined <var>Daemon</var> object. </td></tr>
<tr><th><var>Input</var></th>
<tr><th><var>Input</var></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 an object passed to the <var class="term">daemon</var> thread. This object must be deep copyable, as described in: [[Copying objects|"Copying objects"]].   
<ul>
<li>An object passed to the <var class="term">daemon</var> thread. This object must be deep copyable, as described in: [[Copying objects|"Copying objects"]].   
<li>A Boolean value. If a Null object
</ul>
</table>
</table>



Revision as of 16:18, 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.
Input This optional, name allowed, argument is an object passed to the daemon thread. This object must be deep copyable, as described in: "Copying objects".

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

Examples

See also