170 |
@code{scm_must_free}. This section explains why we want you to stop |
@code{scm_must_free}. This section explains why we want you to stop |
171 |
using them, and how to do this. |
using them, and how to do this. |
172 |
|
|
173 |
|
@findex scm_must_malloc |
174 |
|
@findex scm_must_realloc |
175 |
|
@findex scm_must_calloc |
176 |
|
@findex scm_must_free |
177 |
The functions @code{scm_must_malloc} and @code{scm_must_realloc} |
The functions @code{scm_must_malloc} and @code{scm_must_realloc} |
178 |
behaved like @code{scm_gc_malloc} and @code{scm_gc_realloc} do now, |
behaved like @code{scm_gc_malloc} and @code{scm_gc_realloc} do now, |
179 |
respectively. They would inform the GC about the newly allocated |
respectively. They would inform the GC about the newly allocated |
198 |
When this happened, the result was a dramatic increase in (senseless) |
When this happened, the result was a dramatic increase in (senseless) |
199 |
GC activity which would effectively stop the program dead. |
GC activity which would effectively stop the program dead. |
200 |
|
|
201 |
|
@findex scm_done_malloc |
202 |
|
@findex scm_done_free |
203 |
The functions @code{scm_done_malloc} and @code{scm_done_free} were |
The functions @code{scm_done_malloc} and @code{scm_done_free} were |
204 |
introduced to help restore balance to the force, but existing bugs did |
introduced to help restore balance to the force, but existing bugs did |
205 |
not magically disappear, of course. |
not magically disappear, of course. |