From: Marius Vollmer <mvo@zagadka.ping.de>
Cc: guile-devel@gnu.org
Subject: Re: scm_must_free
Date: 27 Aug 2002 00:03:04 +0200 [thread overview]
Message-ID: <87y9at5ld3.fsf@zagadka.ping.de> (raw)
In-Reply-To: <15716.11055.92865.675317@blauw.xs4all.nl>
Han-Wen Nienhuys <hanwen@cs.uu.nl> writes:
> Why does scm_must_free barf on freeing the null pointer?
I don't know. scm_must_free is on its way out anyway so we might not
want to bother. (See scm_gc_malloc etc for the functions that it is
replaced with, in HEAD.)
scm_must_malloc can't return a NULL pointer, so maybe that's the reason.
--
GPG: D5D4E405 - 2F9B BCCC 8527 692A 04E3 331E FAF8 226A D5D4 E405
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
prev parent reply other threads:[~2002-08-26 22:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-22 0:07 scm_must_free Han-Wen Nienhuys
2002-08-26 22:03 ` Marius Vollmer [this message]
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=87y9at5ld3.fsf@zagadka.ping.de \
--to=mvo@zagadka.ping.de \
--cc=guile-devel@gnu.org \
/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).