Code segment unload: Difference between revisions
m
omit from assembly
(Added Wren blurb.) |
Puppydrum64 (talk | contribs) m (omit from assembly) |
||
Line 125:
However, what you can do is to place code that will only be run once, such as initialization code, into a function and then call that. Functions (as opposed to class methods) are first class objects in Wren and will be garbage collected when there are no longer any references to them. This doesn't usually occur immediately but you can request an immediate collection by calling the ''System.gc'' method.
{{omit from|360 Assembly|Depends entirely on the hardware implementation}}
{{omit from|6502 Assembly|Depends entirely on the hardware implementation}}
{{omit from|6800 Assembly|Depends entirely on the hardware implementation}}
{{omit from|68000 Assembly|Depends entirely on the hardware implementation}}
{{omit from|8051 Assembly|Depends entirely on the hardware implementation}}
{{omit from|8080 Assembly|Depends entirely on the hardware implementation}}
{{omit from|8086 Assembly|Depends entirely on the hardware implementation}}
{{omit from|AArch64 Assembly|Depends entirely on the hardware implementation}}
{{omit from|ARM Assembly|Depends entirely on the hardware implementation}}
{{omit from|AWK}}
{{omit from|Brlcad}}
Line 132 ⟶ 140:
{{omit from|Logtalk}}
{{omit from|Mathematica}}
{{omit from|MIPS Assembly|Depends entirely on the hardware implementation}}
{{omit from|MIRC Scripting Language}}
{{omit from|TPP}}
{{omit from|UNIX Shell}}
{{omit from|VAX Assembly|Depends entirely on the hardware implementation}}
{{omit from|X86 Assembly|Depends entirely on the hardware implementation}}
{{omit from|Z80 Assembly|Depends entirely on the hardware implementation}}
{{omit from|ZX Spectrum Basic}}
| |||