unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: stefan <stefan@lkcc.org>
Cc: guile-devel@gnu.org
Subject: Re: [dev-serveez] Re: memory management
Date: Wed, 19 Mar 2003 21:47:07 +0100 (CET)	[thread overview]
Message-ID: <Pine.LNX.4.44.0303192143540.1049-100000@bono.reversers.net> (raw)
In-Reply-To: <8765qgzc9p.fsf@zagadka.ping.de>

On 18 Mar 2003, Marius Vollmer wrote:

> > Would you supply a scm_free() inside libguile.dll there would be no
> > problem, because then the free() called inside libguile.dll:scm_free()
> > would match the previous malloc() (also called inside libguile.dll).
>
> If you can instruct code to use libguile.dll:scm_free instead of
> kernel32.dll:free, can't you also instruct it to use msvcrt.dll:free
> instead of kernel32.dll:free?

I would need to call libguile.dll:libc:free.  I would need to know to
which libc libguile.dll was linked.

BTW:  The standard libc for MinGW is 'msvcrt.dll'.  You get into trouble
      when you want to use another (native) compiler, like BorlandC or
      VisualC.

So what would be the correct solution without scm_free()?

Thanks in advance,
	stefan@lkcc.org



_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel


  reply	other threads:[~2003-03-19 20:47 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-18 18:29 memory management stefan
2003-03-18 19:48 ` Marius Vollmer
2003-03-19 20:47   ` stefan [this message]
2003-03-22 23:53     ` Marius Vollmer

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=Pine.LNX.4.44.0303192143540.1049-100000@bono.reversers.net \
    --to=stefan@lkcc.org \
    --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).