unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Jan D." <jan.h.d@swipnet.se>
Cc: emacs-devel@gnu.org
Subject: Re: Question about GC in C code.
Date: Tue, 12 Nov 2002 13:49:56 +0100 (MET)	[thread overview]
Message-ID: <200211121246.gACCk0MU030988@stubby.bodenonline.com> (raw)
In-Reply-To: <E18BBfp-0002Go-00@fencepost.gnu.org> from "Richard Stallman" at nov 11, 2002 05:20:05

> 
>     But I confess that I have no clue as how GC works in the C code.
>     Will this approach work?  Will menu_bar_vector be safe from GC?
> 
> You have to modify the GC code in alloc.c to explicitly find these
> C data structures in the menus and mark them the vectors by calling
> mark_object.
> 

I think now I got it.  But instead of adding a Gtk-specific solution
I would like to propose a more generic variant.

How about if alloc.c was modified so other code could register a function
to be called when GC occurs?  That function could then mark lisp
objects as needed.  That way we can keep alloc.c free from knowing all
the details of data structures, and changes to those data structures
can be localized in just one file.  Something like this:

typedef void (*mark_function) (Lisp_Object *argptr);
typedef void (*gc_function) (mark_function func);

void
register_gc_function (gc_function func);

Then in the Gtk code I can do:

static void
mark_gtk_data (mark_function func)
{
  /* find menu data and mark */
  ...
  func(&data->menu_bar_vector);
  ...
}

...
  register_gc_function (mark_gtk_data);

The reason for mark_function is that mark_object is static in alloc.c, so
I pass it as an argument to gc_function.

Is this feasible?

	Jan D.

  parent reply	other threads:[~2002-11-12 12:49 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-09 20:36 Question about GC in C code Jan D.
2002-11-11 10:20 ` Richard Stallman
2002-11-11 14:25   ` Jan D.
2002-11-12 12:49   ` Jan D. [this message]
2002-11-12 19:44     ` Stefan Monnier
2002-11-14  4:10     ` Richard Stallman
2002-11-14  6:18       ` Jan D.
2002-11-16  1:34         ` Richard Stallman
2002-11-16 12:37           ` Jan D.
2002-11-17  5:14             ` Richard Stallman

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/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200211121246.gACCk0MU030988@stubby.bodenonline.com \
    --to=jan.h.d@swipnet.se \
    --cc=emacs-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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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).