From: Kevin Ryde <user42@zip.com.au>
Subject: scm_must_malloc indexing
Date: Sat, 09 Aug 2003 08:07:56 +1000 [thread overview]
Message-ID: <874r0rdcqr.fsf@zip.com.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 122 bytes --]
FYI,
* scheme-memory.texi (Memory Blocks): Add index entries for deprecated
scm_must_malloc and friends.
[-- Attachment #2: scheme-memory.texi.must-index.diff --]
[-- Type: text/plain, Size: 931 bytes --]
--- scheme-memory.texi.~1.14.~ 2003-06-12 08:41:53.000000000 +1000
+++ scheme-memory.texi 2003-08-08 18:34:58.000000000 +1000
@@ -170,6 +170,10 @@
@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 @@
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.
[-- Attachment #3: Type: text/plain, Size: 142 bytes --]
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
reply other threads:[~2003-08-08 22:07 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=874r0rdcqr.fsf@zip.com.au \
--to=user42@zip.com.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).