Code segment unload: Difference between revisions

Content added Content deleted

Inline

@@ Line 77: / Line 77: @@
 other than to perhaps "daisy-chain" executables. You could wrap FreeLibrary/dlcose as per OpenOneDLL() in builtins/VM/pcfunc.e.
-For interpreted programs however, the code is built and executed in dynamically allocated memory, and in fact "p -test" runs
+For interpreted programs however, the code is built and executed in dynamically allocated memory, and in fact "p -test" runs some 60 separate test programs, some of which are deliberately memory-intensive. For each one it allocates a full execution environment, including code space, a call stack, and new heap, and tears it all down and reclaims the memory on completion. That process is, fairly obviously, quite involved and not for the faint hearted, but clearly doable.
-some 60 separate test programs, some of which are deliberately memory-intensive. For each one the compiler allocates a full
-execution environment, including code space, a call stack, and new heap, and tears it all down and reclaims the memory on
-completion. That process is, fairly obviously, quite involved and not for the faint hearted, but clearly doable.
 =={{header|Python}}==