From: Bakul Shah <bakul@bitblocks.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] rsc's libtask on embedded
Date: Thu, 9 Jul 2015 09:31:15 -0700 [thread overview]
Message-ID: <960EE432-0DA7-45DB-8A35-4A0FF3A3D0DB@bitblocks.com> (raw)
In-Reply-To: <05F47572-DCD2-4AF1-9C84-0BFD846492B3@quintile.net>
Your use is different and simple enough that I would suggest doing this from scratch in pure C. Or start from an existing setjmp based implementation. It should really be a couple pages of code at most.
> On Jul 9, 2015, at 9:12 AM, "steve@quintile.net" <steve@quintile.net> wrote:
>
> co routines plus channels is exactly what I want.
next prev parent reply other threads:[~2015-07-09 16:31 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-09 8:38 Steve Simon
2015-07-09 14:17 ` Joseph Stewart
2015-07-09 14:50 ` Steve Simon
2015-07-09 15:09 ` David du Colombier
2015-07-09 15:52 ` Joseph Stewart
2015-07-09 15:55 ` Joseph Stewart
2015-07-09 15:51 ` Bakul Shah
2015-07-09 15:58 ` Joseph Stewart
2015-07-09 16:12 ` steve
2015-07-09 16:31 ` Bakul Shah [this message]
2015-07-09 16:50 ` Skip Tavakkolian
2015-07-10 2:07 ` erik quanstrom
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=960EE432-0DA7-45DB-8A35-4A0FF3A3D0DB@bitblocks.com \
--to=bakul@bitblocks.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).