unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: Egil Moeller <redhog@redhog.org>
Subject: Re: out-of-order GC
Date: Wed, 1 Jan 2003 11:57:03 +0100 (CET)	[thread overview]
Message-ID: <Pine.LNX.4.30.0301011154140.1884-100000@urd.norna.redhog.org> (raw)
In-Reply-To: <m3smwendzl.fsf@laruns.ossau.uklinux.net>

>    Fortunately, resource smobs can check, in their free functions,
>    whether this has happened, by looking at the SCM_TYP16 of their
>    reference to the display smob.  If the display smob is still valid,
>    this will be scm_tc16_xdisplay, and the relevant X resource should
>    be freed as normal.  If the display smob has been freed earlier in
>    this sweep, GC will have set its SCM_TYP16 to scm_tc_free_cell;
>    this indicates that XCloseDisplay has already been called, and so
>    the relevant X resource no longer needs to be freed. */

Aha, so that's how it should be done. Is it the pointer (on the resource
SMOB), or the diplay SMOB itself that is marked? And in the latter cae,
what if the space has allready been reused, or can't that happend? And
what is the name of the C function to check the pointer for what type it
is?

Regards,
Egil

-- 
http://redhog.org
GPG Public key: http://redhog.org/PGP%20Public%20key.asc
Hi! I'm a .signature virus! Copy me into your ~/.signature to help me spread!



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


  reply	other threads:[~2003-01-01 10:57 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-29 16:36 out-of-order GC Egil Moeller
2002-12-30 13:36 ` Greg Troxel
2002-12-30 14:05   ` Egil Moeller
2002-12-31  3:06     ` Matt Hellige
2002-12-31 20:13     ` Neil Jerram
2003-01-01 10:57       ` Egil Moeller [this message]
2003-01-01 17:58         ` Neil Jerram
2003-01-01 21:22         ` 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.30.0301011154140.1884-100000@urd.norna.redhog.org \
    --to=redhog@redhog.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).