From: Nala Ginrut <nalaginrut@gmail.com>
To: Andy Wingo <wingo@pobox.com>
Cc: guile-devel <guile-devel@gnu.org>
Subject: Re: wip-threads-and-fork
Date: Sun, 26 Feb 2012 10:35:20 +0800 [thread overview]
Message-ID: <CAPjoZochwPdOuCe6qPQnRmff6A2dqGD8fRFDCtiyPuLf7Fm0MQ@mail.gmail.com> (raw)
In-Reply-To: <87zkc694iq.fsf@pobox.com>
[-- Attachment #1: Type: text/plain, Size: 697 bytes --]
On Sun, Feb 26, 2012 at 2:01 AM, Andy Wingo <wingo@pobox.com> wrote:
> Hi!
>
> On Sat 25 Feb 2012 03:30, Nala Ginrut <nalaginrut@gmail.com> writes:
>
> > 'primitive-fork' shouldn't be removed directly according to
> > previous discussion, unless the user chosen ptheads. If they do not
> > use threads, then primitive-fork would be useful, is that right?
>
> Indeed. In Guile master, primitive-fork is always there (if your system
> supports fork). However, invoking it will raise an error if you have
> created other threads. You can only use it before creating threads.
>
> Is that good for your purposes?
>
>
All right, I think my problem is done ;-)
> Andy
> --
> http://wingolog.org/
>
[-- Attachment #2: Type: text/html, Size: 1395 bytes --]
next prev parent reply other threads:[~2012-02-26 2:35 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-08 22:10 wip-threads-and-fork Andy Wingo
2012-02-22 21:40 ` wip-threads-and-fork Andy Wingo
2012-02-23 15:05 ` wip-threads-and-fork Andy Wingo
2012-02-23 15:49 ` wip-threads-and-fork Nala Ginrut
2012-02-23 16:13 ` wip-threads-and-fork Andy Wingo
2012-02-24 3:00 ` wip-threads-and-fork Nala Ginrut
2012-02-24 10:21 ` wip-threads-and-fork Andy Wingo
2012-02-24 14:08 ` wip-threads-and-fork Nala Ginrut
2012-02-24 14:47 ` wip-threads-and-fork Andy Wingo
2012-02-24 15:25 ` wip-threads-and-fork Nala Ginrut
2012-02-26 22:03 ` wip-threads-and-fork Ludovic Courtès
2012-02-27 9:44 ` wip-threads-and-fork Andy Wingo
2012-03-01 19:40 ` wip-threads-and-fork Ludovic Courtès
2012-02-24 18:57 ` wip-threads-and-fork Andy Wingo
2012-02-25 2:21 ` wip-threads-and-fork Nala Ginrut
2012-02-25 2:30 ` wip-threads-and-fork Nala Ginrut
2012-02-25 18:01 ` wip-threads-and-fork Andy Wingo
2012-02-26 2:35 ` Nala Ginrut [this message]
2012-02-26 22:00 ` wip-threads-and-fork Ludovic Courtès
2012-02-27 9:39 ` wip-threads-and-fork Andy Wingo
2012-03-01 19:35 ` wip-threads-and-fork Ludovic Courtès
2012-03-03 16:32 ` wip-threads-and-fork Andy Wingo
2012-03-03 21:20 ` wip-threads-and-fork Ludovic Courtès
2012-03-04 11:38 ` wip-threads-and-fork Andy Wingo
2012-03-21 21:26 ` wip-threads-and-fork Ludovic Courtès
2012-03-22 2:48 ` wip-threads-and-fork Nala Ginrut
2012-03-23 9:40 ` wip-threads-and-fork Andy Wingo
2012-03-27 15:54 ` wip-threads-and-fork Ludovic Courtès
2012-04-06 18:30 ` wip-threads-and-fork Andy Wingo
2012-04-07 22:54 ` wip-threads-and-fork Ludovic Courtès
2013-01-17 11:41 ` wip-threads-and-fork Andy Wingo
2012-03-01 19:32 ` wip-threads-and-fork Ludovic Courtès
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=CAPjoZochwPdOuCe6qPQnRmff6A2dqGD8fRFDCtiyPuLf7Fm0MQ@mail.gmail.com \
--to=nalaginrut@gmail.com \
--cc=guile-devel@gnu.org \
--cc=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).