From mboxrd@z Thu Jan 1 00:00:00 1970 Path: main.gmane.org!not-for-mail From: Egil Moeller Newsgroups: gmane.lisp.guile.user Subject: Re: out-of-order GC Date: Wed, 1 Jan 2003 11:57:03 +0100 (CET) Sender: guile-user-bounces+guile-user=m.gmane.org@gnu.org Message-ID: References: Reply-To: redhog@redhog.org NNTP-Posting-Host: main.gmane.org Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Trace: main.gmane.org 1041434180 13742 80.91.224.249 (1 Jan 2003 15:16:20 GMT) X-Complaints-To: usenet@main.gmane.org NNTP-Posting-Date: Wed, 1 Jan 2003 15:16:20 +0000 (UTC) Return-path: Original-Received: from monty-python.gnu.org ([199.232.76.173]) by main.gmane.org with esmtp (Exim 3.35 #1 (Debian)) id 18TkbT-0003ZV-00 for ; Wed, 01 Jan 2003 16:16:19 +0100 Original-Received: from localhost ([127.0.0.1] helo=monty-python.gnu.org) by monty-python.gnu.org with esmtp (Exim 4.10.13) id 18TkaL-0004kP-00 for guile-user@m.gmane.org; Wed, 01 Jan 2003 10:15:09 -0500 Original-Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13) id 18TkZa-0004c3-00 for guile-user@gnu.org; Wed, 01 Jan 2003 10:14:22 -0500 Original-Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13) id 18TkYp-0004J7-00 for guile-user@gnu.org; Wed, 01 Jan 2003 10:13:37 -0500 Original-Received: from q94.ryd.student.liu.se ([130.236.217.94] helo=redhog.org) by monty-python.gnu.org with esmtp (Exim 4.10.13) id 18TkY1-0003hq-00 for guile-user@gnu.org; Wed, 01 Jan 2003 10:12:45 -0500 Original-Received: from localhost (localhost.localdomain [127.0.0.1]) by redhog.org (Postfix) with ESMTP id 8EBD35FA22 for ; Wed, 1 Jan 2003 11:57:04 +0100 (CET) X-Sender: Original-To: In-Reply-To: X-BeenThere: guile-user@gnu.org X-Mailman-Version: 2.1b5 Precedence: list List-Id: General Guile related discussions List-Help: List-Post: List-Subscribe: , List-Archive: List-Unsubscribe: , Errors-To: guile-user-bounces+guile-user=m.gmane.org@gnu.org Xref: main.gmane.org gmane.lisp.guile.user:1493 X-Report-Spam: http://spam.gmane.org/gmane.lisp.guile.user:1493 > 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