From: David Leimbach <leimy2k@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] OT concurrent C
Date: Thu, 3 Dec 2009 06:32:02 -0800 [thread overview]
Message-ID: <3e1162e60912030632y4eece9f5k8985f779d406a772@mail.gmail.com> (raw)
In-Reply-To: <9d63f743b1604dea527b84839288293c@hera.eonet.ne.jp>
[-- Attachment #1: Type: text/plain, Size: 455 bytes --]
libdispatch is in FreeBSD now, and people are using it to write concurrent C
code. I think they even have blocks, and the clang compiler front end
working too. I believe the earliest, least-experimental branch of code is
FreeBSD-STABLE for the 8 series, but I'll double check.
Dave
On Thu, Dec 3, 2009 at 3:14 AM, <kokamoto@hera.eonet.ne.jp> wrote:
> > distant ancestor of alef?
>
> and alef's descent may be Go.☺
>
> Kenji
>
>
>
[-- Attachment #2: Type: text/html, Size: 741 bytes --]
prev parent reply other threads:[~2009-12-03 14:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-03 10:12 Steve Simon
2009-12-03 11:14 ` kokamoto
2009-12-03 14:32 ` David Leimbach [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3e1162e60912030632y4eece9f5k8985f779d406a772@mail.gmail.com \
--to=leimy2k@gmail.com \
--cc=9fans@9fans.net \
/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 NNTP newsgroup(s).