9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "steve@quintile.net" <steve@quintile.net>
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 17:12:10 +0100	[thread overview]
Message-ID: <05F47572-DCD2-4AF1-9C84-0BFD846492B3@quintile.net> (raw)
In-Reply-To: <CANGQBe5VFA6ky8TnHpuLcgxg2+Pxph97_H7uSgiFPEKwZbPFhQ@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1205 bytes --]

I looked at proto, they are just state machines pretending to be threads (imho) - not my style.

libtask for me, I hope I can slice it a little and put the non-bear-metal bits in seperate files so I can offer the changes back.

co routines plus channels is exactly what I want.

-Steve





> On 9 Jul 2015, at 16:58, Joseph Stewart <joseph.stewart@gmail.com> wrote:
> 
> One other thing that I've looked at but never used is Adam Dunkels' "protothreads" (http://dunkels.com/adam/pt/) although you'd still need to roll your own channel library.
> 
>> On Thu, Jul 9, 2015 at 10:50 AM, Steve Simon <steve@quintile.net> wrote:
>> The system I am trying to add libtask to has no runtime other than libc.
>> 
>> Corrently it is an even based system that uses a "min main loop" and
>> a twisty maze of nested state machines that all look the same.
>> 
>> Hence my desire to add co-routines + channels (i.e. exactly what libtask is)
>> to it. I have no need for the file or network modules but those are easily removed.
>> 
>> I don't have the context calls but I do have setjmp/longjmp so that is what I
>> am trying to use.
>> 
>> I will shout if it works out.
>> 
>> -Steve
> 

[-- Attachment #2: Type: text/html, Size: 1958 bytes --]

  reply	other threads:[~2015-07-09 16:12 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 [this message]
2015-07-09 16:31         ` Bakul Shah
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=05F47572-DCD2-4AF1-9C84-0BFD846492B3@quintile.net \
    --to=steve@quintile.net \
    --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).