From: ludo@gnu.org (Ludovic Courtès)
To: guile-user@gnu.org
Subject: Re: reallocating data not covered by gc
Date: Wed, 26 Sep 2007 20:47:48 +0200 [thread overview]
Message-ID: <873ax19sbv.fsf@chbouib.org> (raw)
In-Reply-To: 20070924.143114.20498248.schilling.klaus@web.de
Hi,
Klaus Schilling <schilling.klaus@web.de> writes:
> Is it dangerous to reallocate from scheme wrapper code
> pointers that have been allocated or
> declared NULL in code that was executed before boot_guile was called?
Guile doesn't care about what you do with libc's malloc/realloc/etc. so
you can essentially use them to do whatever pleases you. :-)
> does declaring critical sections arround those reallocation calls
> smoothen the situation?
Critical sections are unrelated: they are supposedly a way to block
execution of asyncs (although it's not all that clear from looking at
the code, especially since `scm_i_critical_section_mutex' doesn't seem
to be really used...).
Thanks,
Ludovic.
_______________________________________________
Guile-user mailing list
Guile-user@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-user
prev parent reply other threads:[~2007-09-26 18:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-24 12:31 reallocating data not covered by gc Klaus Schilling
2007-09-26 18:47 ` Ludovic Courtès [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=873ax19sbv.fsf@chbouib.org \
--to=ludo@gnu.org \
--cc=guile-user@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).