Code segment unload: Difference between revisions
Content added Content deleted
m (→{{header|REXX}}: added the REXX computer programming language for this task.) |
No edit summary |
||
Line 41: | Line 41: | ||
=={{header|Java}}== |
=={{header|Java}}== |
||
The situation for Java is as described below in the entry for its sister JVM language, Kotlin. |
The situation for Java is as described below in the entry for its sister JVM language, Kotlin. |
||
=={{header|Julia}}== |
|||
Julia's functions are compiled and their code allocated memory "just in time" the first time their |
|||
code is run. Usually, memory used within a function can be dynamically garbage collected once that |
|||
data is out of scope. To also garbage collect the memory used by a function's code, it would be |
|||
necessary to define and run a new function with the same name and argument types, which would allow |
|||
the prior function's code memory to be reclaimed. In practice, this is seldom needed or done, |
|||
since most memory usage in Julia is for data, not code. |
|||
=={{header|Kotlin}}== |
=={{header|Kotlin}}== |