public inbox for guile-emacs@sourceware.org
 help / color / mirror / Atom feed
From: Mikael Djurfeldt <mdj@mdj-pc.nada.kth.se>
To: Ken Raeburn <raeburn@raeburn.org>
Cc: djurfeldt@nada.kth.se
Subject: Re: guile and emacs
Date: Sat, 28 Aug 1999 13:48:00 -0000	[thread overview]
Message-ID: <xy7lnavpr8w.fsf@mdj-pc.nada.kth.se> (raw)
In-Reply-To: <199908281821.OAA14563@raeburn.org>

Ken Raeburn <raeburn@raeburn.org> writes:

> 2) he's got some "issues" with Guile's implementation decisions,
> including the use of conservative GC.  What he's saying makes sense,
> so I'll be looking a bit at separating further into "Lisp" vs "general
> Scheme" vs "Guile" bits what I've done so far.  (GC will be an
> interesting issue though; I've got some thoughts on that.)

I'm curious about what he has to say on Guile implementation
decisions.  Could you give me a reference?

Also, regarding conservative GC, making a generic interface to the
Scheme interpreter is no solution.  If you have an interface which
would work for both an interpreter using a conservative GC and one
using precise GC, you could just as well take the one with precise GC.

The major gain of conservative GC is that the interface becomes
simpler and less bug prone.

I have only limited experience in running Guile for longer times, but
I have had scwm running for several days without problems, and a
friend of mine has a server application which also runs for long
without problems.  This makes me doubt that there is a problem in
practise with using conservative GC.

/mdj

  reply	other threads:[~1999-08-28 13:48 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 [this message]
1999-09-08 12:43 ` Jim Blandy
1999-09-08 12:57 ` Jim Blandy
1999-09-08 14:30   ` Mikael Djurfeldt

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=xy7lnavpr8w.fsf@mdj-pc.nada.kth.se \
    --to=mdj@mdj-pc.nada.kth.se \
    --cc=djurfeldt@nada.kth.se \
    --cc=raeburn@raeburn.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).