public inbox for guile-emacs@sourceware.org
 help / color / mirror / Atom feed
From: Mikael Djurfeldt <mdj@mdj-pc.nada.kth.se>
To: Jim Blandy <jimb@red-bean.com>
Cc: djurfeldt@nada.kth.se
Subject: Re: guile and emacs
Date: Wed, 08 Sep 1999 14:30:00 -0000	[thread overview]
Message-ID: <xy7d7vtxfdb.fsf@mdj-pc.nada.kth.se> (raw)
In-Reply-To: <npogfdfa9d.fsf@zwingli.cygnus.com>

Jim Blandy <jimb@red-bean.com> writes:

> For example, note that the code below is incorrect in Emacs.  Assume
> all functions return Lisp_Object values:
> 
> 	foo (bar (), baz ())
> 
> Suppose the compiler calls bar first, then baz.  While baz runs, foo's
> frame holds a reference to bar's return value --- possibly the only
> one.  If collection can occur in baz, then bar's return value will be
> collected.  Instead, you must write:
> 
> 	{
> 	  Lisp_Object temp = Qnil;
> 	  GCPRO1 (temp);
> 
> 	  temp = bar ();
> 	  foo (temp, baz ());
> 	}
> 
> But for anyone who has not worked on both Guile and Emacs, these
> arguments are anecdotal, and the usual way of thinking about program
> design suggests the opposite conclusion.  So I don't know what to do.
> Any suggestions?

I think sharing your experience with precise vs conservative GC is one
important thing.  We could also try to sift the archives for
discussions on this topic.

I think it would be a really big mistake to settle for an interface
compatible with precise GC if the problems with conservative GC are
just phantoms.

      reply	other threads:[~1999-09-08 14:30 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-08-28 11:21 Ken Raeburn
1999-08-28 13:48 ` Mikael Djurfeldt
1999-09-08 12:43 ` Jim Blandy
1999-09-08 12:57 ` Jim Blandy
1999-09-08 14:30   ` Mikael Djurfeldt [this message]

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

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

  git send-email \
    --in-reply-to=xy7d7vtxfdb.fsf@mdj-pc.nada.kth.se \
    --to=mdj@mdj-pc.nada.kth.se \
    --cc=djurfeldt@nada.kth.se \
    --cc=jimb@red-bean.com \
    /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).