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: Thu, 14 Nov 2002 07:18:57 +0100 (MET)	[thread overview]
Message-ID: <200211140614.gAE6EvMU031551@stubby.bodenonline.com> (raw)
In-Reply-To: <E18CBKL-0005IZ-00@fencepost.gnu.org> from "Richard Stallman" at nov 13, 2002 11:10:01

> 
>     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.
> 
> Would it really make a big difference?  I don't see it.  It would be a
> simplification in something already simple, that is only done very
> rarely.  Why do you think this would be a big improvement?

The thing is I don't think I can guarantee that it will be rarely.
Since Gtk is new and some issues not really solved (tooltips in
menus, Gtk toolbar), I expect more Lisp_Objects may be needed in
Gtk callback data.  I would prefer to be able to make local changes
in a Gtk only file rather that propagate these changes into files
that really have nothing to do with GUI toolkits.

Also, I think minimizing the number of files that have to have
tests for USE_GTK is a good thing.

	Jan D.

  reply	other threads:[~2002-11-14  6:18 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.
2002-11-12 19:44     ` Stefan Monnier
2002-11-14  4:10     ` Richard Stallman
2002-11-14  6:18       ` Jan D. [this message]
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=200211140614.gAE6EvMU031551@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).