ContinueIndependently (Daemon subroutine): Difference between revisions
Jump to navigation
Jump to search
mNo edit summary |
m (→Syntax terms) |
||
| Line 10: | Line 10: | ||
<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 22:42, 21 May 2012
Continue processing independently 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, ContinueIndependently returns immediately, thus allowing the thread that issued ContinueIndependently to run in parallel with the daemon thread. Unlike ContinueAsynchronously, this method makes the daemon thread completely independent of the parent thread, so the daeamon is no longer available.
Syntax
daemon:ContinueIndependently[( [Input= object])] Throws DaemonLost, IncorrectDaemonState
Syntax terms
| daemon | A previously defined Daemon object. |
|---|---|
| object | This optional, name allowed, argument is either:
|
Usage notes
- Issuing ContinueIndependently against a daemon not in a ReturnToMaster wait results in an IncorrectDaemonState exception.
- The Continue and ContinueAsynchronously methods also tell a daemon to continue from a ReturnToMaster wait.