From: Andy Wingo <wingo@pobox.com>
Subject: Re: scm_i_fraction_reduce thread safety
Date: Sun, 01 Feb 2004 20:49:14 +0200 [thread overview]
Message-ID: <1075661354.3257.71.camel@localhost> (raw)
In-Reply-To: <xy77jz97awn.fsf@chunk.mit.edu>
On Fri, 2004-01-30 at 16:45, Mikael Djurfeldt wrote:
> My view is that the current organization of threading in HEAD has a
> lot of promise. It does give full concurrency, at the same time as it
> is usually quite easy to program for.
I don't have anything really constructive to add, but I do want to say
that concurrent threads would be wonderful. If you ever check the docs
for the python gstreamer bindings[1], you'll see the mess they get into
because the python interpreter is single-threaded (due to their
refcounting gc strategy). So really you can't write a quality DVD player
in python, because the callbacks and signals coming in from many threads
have to compete over one mutex.
So. Just a note of support for your efforts, they would be much
appreciated in media-land.
--
Andy Wingo <wingo@pobox.com>
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2004-02-01 18:49 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-11 11:43 scm_i_fraction_reduce thread safety Bill Schottstaedt
2003-12-11 19:19 ` Carl Witty
2003-12-12 12:11 ` Bill Schottstaedt
2003-12-12 15:04 ` Paul Jarc
2003-12-12 23:23 ` Kevin Ryde
2004-01-10 22:38 ` Marius Vollmer
2004-01-10 23:29 ` Kevin Ryde
2004-01-11 1:31 ` Marius Vollmer
2004-01-12 0:51 ` Kevin Ryde
2004-01-12 5:22 ` Richard Todd
2004-01-14 21:09 ` Kevin Ryde
2004-01-21 0:03 ` Marius Vollmer
2004-01-21 0:00 ` Marius Vollmer
2004-01-21 3:11 ` Carl Witty
2004-01-21 21:06 ` Marius Vollmer
2004-01-27 22:15 ` Dirk Herrmann
2004-01-27 23:24 ` Rob Browning
2004-01-29 19:35 ` Marius Vollmer
2004-01-29 20:32 ` Rob Browning
2004-01-30 14:45 ` Mikael Djurfeldt
2004-02-01 18:49 ` Andy Wingo [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-12-09 20:39 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=1075661354.3257.71.camel@localhost \
--to=wingo@pobox.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).