diff options
author | Kevin Ryde <user42@zip.com.au> | 2003-08-08 22:08:25 +0000 |
---|---|---|
committer | Kevin Ryde <user42@zip.com.au> | 2003-08-08 22:08:25 +0000 |
commit | 8510ef7a1b22a9d718a4c4f179cc89fdc815a7eb (patch) | |
tree | 3554fd367b94427662d09cadbc213f7fb118bfa0 /doc/ref/scheme-memory.texi | |
parent | 8e5b4b9e34736010dbd74f02331735490f9d4661 (diff) | |
download | guile-8510ef7a1b22a9d718a4c4f179cc89fdc815a7eb.tar.gz |
(Memory Blocks): Add index entries for deprecated scm_must_malloc and friends.
Diffstat (limited to 'doc/ref/scheme-memory.texi')
-rw-r--r-- | doc/ref/scheme-memory.texi | 6 |
1 files changed, 6 insertions, 0 deletions
diff --git a/doc/ref/scheme-memory.texi b/doc/ref/scheme-memory.texi index 443e33ea4..6ea74886e 100644 --- a/doc/ref/scheme-memory.texi +++ b/doc/ref/scheme-memory.texi @@ -170,6 +170,10 @@ previous section. In their place, it had the functions @code{scm_must_free}. This section explains why we want you to stop using them, and how to do this. +@findex scm_must_malloc +@findex scm_must_realloc +@findex scm_must_calloc +@findex scm_must_free The functions @code{scm_must_malloc} and @code{scm_must_realloc} behaved like @code{scm_gc_malloc} and @code{scm_gc_realloc} do now, respectively. They would inform the GC about the newly allocated @@ -194,6 +198,8 @@ of sync with reality and could even overflow in long running programs. When this happened, the result was a dramatic increase in (senseless) GC activity which would effectively stop the program dead. +@findex scm_done_malloc +@findex scm_done_free The functions @code{scm_done_malloc} and @code{scm_done_free} were introduced to help restore balance to the force, but existing bugs did not magically disappear, of course. |