Manual:DIL Manual/secure() - Revision history

Nove: XML import

2025-12-04T22:33:52Z

XML import

Papi: XML import of LLM wiki pages

2025-12-04T10:44:03Z

XML import of LLM wiki pages

Papi at 22:04, 13 August 2022

2022-08-13T22:04:18Z

Papi at 18:48, 13 August 2022

2022-08-13T18:48:03Z

Papi at 18:22, 13 August 2022

2022-08-13T18:22:40Z

Nove: XML import

2020-05-27T13:08:08Z

XML import

New page

<span id="bpsec"></span>
secure ( u : unitptr , label )
u : Unit to secure.
label : Label to jump to, on removal.
result: Secures a unitptr, so that the program will go to 'label'
if unit leaves local environment. If this happens, during
a call to another function/procedure, it will continue
at that label when the function/procedure returns.
If you perform some kind of call to a template, the removing
of a unit from the local environment will not have affect.
until the return from that function, as the program execution
will continue at the designated label after a call. Should
several secured units leave local environment, the last such
event will determine the point of execution upon return.

@@ Line 16: / Line 16: @@
 * When the DIL program calls cast(), cast2() or attackspell(), meleeattack(), meleedamage().
 * Returning from a DIL sub-function that has triggered a secure() scan.
-* In every foreach-next step [needs to be evaluated further]
+* In every foreach-next step
 A DIL program will test a specific unit for secure in the follow circumstances:

@@ Line 8: / Line 8: @@
 Secures a unitptr, so that the program will go to 'label' if unit leaves local environment.
 The unit leaves the local environment when it is destroyed or e.g. moved to a different location
-such as an adjacent room. A transparent room in a room would not coust as leaving the local environment.
+such as an adjacent room. A transparent room in a room would not count as leaving the local environment.
 A DIL program is tested for secures in the follow circumstances:

@@ Line 1: / Line 1: @@
+<span id="bpsec"></span>
+ secure ( u : unitptr , label )
 <span id="bpsec"></span>
   secure ( u : unitptr , label )

@@ Line 1: / Line 1: @@
-  u : Unit to secure.
+<span id="bpsec"></span>
-  label : Label to jump to, on removal.
+ secure ( u : unitptr , label )
+    u : Unit to secure.
-Secures a unitptr, so that the program will go to 'label' if unit leaves local environment.
+    label : Label to jump to, on removal.
-The unit leaves the local environment when it is destroyed or e.g. moved to a different location
+    result: Secures a unitptr, so that the program will go to 'label'
-such as an adjacent room. A transparent room in a room would not count as leaving the local environment.
+            if unit leaves local environment. If this happens, during
+            a call to another function/procedure, it will continue
-A DIL program is tested for secures in the follow circumstances:
+            at that label when the function/procedure returns.
-* When the DIL program is activated (e.g. after a pause / wait())
+            If you perform some kind of call to a template, the removing
-* When the DIL program has performed a send(), sendto(), sendtoall(), sendtoalldil().
+            of a unit from the local environment will not have affect.
-* When the DIL program calls updateposition() (because it might kill the unit)
+            until the return from that function, as the program execution
-* When the DIL program calls cast(), cast2() or attackspell(), meleeattack(), meleedamage().
+            will continue at the designated label after a call. Should
-* Returning from a DIL sub-function that has triggered a secure() scan.
+            several secured units leave local environment, the last such
-* In every foreach-next step
+            event will determine the point of execution upon return.