unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: ludovic.courtes@laas.fr (Ludovic Courtès)
Cc: Guile Development <guile-devel@gnu.org>
Subject: Re: Serious GC problem in HEAD
Date: Thu, 30 Nov 2006 16:11:09 +0100	[thread overview]
Message-ID: <87y7ptnf5e.fsf@laas.fr> (raw)
In-Reply-To: <874pshddzm.fsf@zip.com.au> (Kevin Ryde's message of "Thu, 30 Nov 2006 10:34:05 +1100")

Hi,

Kevin Ryde <user42@zip.com.au> writes:

> There's really no need to remove globals for their own sake, only one
> gc ever runs of course ...

The point in removing them is to clarify the flow of information, that
is, how GC stats are updated and used.  Believe me, it _was_ hard to
follow with globals.  And Guile is about functional programming, isn't
it?  ;-)

> I've lost track of what it actually improves or fixes :-).

It's mostly a "cleanup" patch:

http://lists.gnu.org/archive/html/guile-devel/2005-12/msg00095.html
http://lists.gnu.org/archive/html/guile-devel/2006-01/msg00009.html

Thanks,
Ludovic.


_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-devel


  reply	other threads:[~2006-11-30 15:11 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-05  8:51 A guile story Neil Jerram
2006-11-05 13:20 ` Andy Wingo
2006-11-05 21:42   ` Neil Jerram
2006-11-06  9:12     ` Ludovic Courtès
2006-11-07 10:24       ` Neil Jerram
2006-11-07 13:01         ` Ludovic Courtès
2006-11-05 23:22   ` Neil Jerram
2006-11-06  9:24 ` Serious GC problem in HEAD Ludovic Courtès
2006-11-07 10:19   ` Neil Jerram
2006-11-07 12:51     ` Ludovic Courtès
2006-11-08 10:00   ` Ludovic Courtès
2006-11-19 15:02     ` Neil Jerram
2006-11-20 13:09       ` Ludovic Courtès
2006-11-29 23:34     ` Kevin Ryde
2006-11-30 15:11       ` Ludovic Courtès [this message]
2006-11-28 20:09 ` A guile story Kevin Ryde

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

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

  git send-email \
    --in-reply-to=87y7ptnf5e.fsf@laas.fr \
    --to=ludovic.courtes@laas.fr \
    --cc=guile-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. 
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).