unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Marius Vollmer <mvo@zagadka.de>
Cc: guile-devel@gnu.org
Subject: Re: threadsafe format.scm
Date: Mon, 15 Sep 2003 15:33:48 +0200	[thread overview]
Message-ID: <878yoqi3b7.fsf@zagadka.ping.de> (raw)
In-Reply-To: <200307302246.16240.clinton@unknownlamer.org> (Clinton Ebadi's message of "Wed, 30 Jul 2003 22:46:15 -0400")

Clinton Ebadi <clinton@unknownlamer.org> writes:

> I moved all of the global definitions into a new format procedure that has a 
> really long letrec. This should be entirely threadsafe.

Great, thanks!  I have installed this.  We don't need papers for it
since the change itself, although affecting everything, is quite
small.

> I'm not sure how Guile does evaluation of procedures once they have
> been evaluated once, so I'm not entirely sure if this has a huge
> amount of overhead or not.

There shouldn't be too much overhead.  It will be slower than with
globals (probably, I would have to benchmark it to be sure), but not
much.  However, the letrec _is_ pretty big and environment access in
Guile is O(n), so well...

-- 
GPG: D5D4E405 - 2F9B BCCC 8527 692A 04E3  331E FAF8 226A D5D4 E405


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


      parent reply	other threads:[~2003-09-15 13:33 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-29  3:27 threadsafe format.scm Clinton Ebadi
2003-07-30 22:36 ` Kevin Ryde
2003-07-30 23:06   ` Clinton Ebadi
2003-07-31  2:46     ` Clinton Ebadi
2003-07-31 22:11       ` Kevin Ryde
2003-08-01  2:39         ` Clinton Ebadi
2003-08-01  3:18           ` Clinton Ebadi
2003-09-15 13:33       ` Marius Vollmer [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

  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=878yoqi3b7.fsf@zagadka.ping.de \
    --to=mvo@zagadka.de \
    --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).