[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: SV: A CSP library "for dummies"?
Why not upload the new files to sourceforge. The files there are dated
Mar 30, 2005 (not that old means out of date..)
On Tue, 2009-02-03 at 09:28 +0000, Teig, Oyvind UTCFS wrote:
> -- libcsp and libcsp2 --
> I have had contact with Richard Beton last fall. He wrote libcsp
> rick.beton at gmail.com
> Bernhard H.C. Sputh has progressed on it, and it's now called libcsp2
> bernhard.sputh at gmx.net
> The sources are at:
> But Bernhard sent me a newer set of files.
> (That being said, we have soon a library finished from the bottom for use on small microcontrollers with 32 KB FLASH and 4 KB RAM. Commstime runs fine. But we have not started to, or even 100% decided to - use it. And it would probably stay internal... It took one experienced guy (me) plus one clever guy (him) 1-2 weeks to do it! We call it CHAN_KIT.)
> I know this is published on the internet.
> Med vennlig hilsen / sincerely
> Ãyvind Teig
> Ãyvind Teig
> Senior dev.eng./utviklingsingeniÃr, M.Sc.
> Autronica Fire and Security AS
> A UTC Fire & Security Company
> Tlf: +47 7358 2468
> Fax: +47 7358 2502
> Mob: +47 9596 1506
> home.no.net/oyvteig/pub - Publications
> > -----Opprinnelig melding-----
> > Fra: Mailing_List_Robot [mailto:sympa@xxxxxxxxxx] PÃ vegne av
> > Ruth Ivimey-Cook
> > Sendt: 2. februar 2009 22:19
> > Til: occam-com
> > Emne: A CSP library "for dummies"?
> > Folks,
> > Is there a CSP-type threads library that is compilable using
> > only a C compiler on Windows/MacOSX/Linux?
> > I'm trying to wean some folks at work off pthreads and suggested
> > libc++csp, but it's C++ roots rule it out. I guess it could
> > probably be
> > ported, but that's not going to make it more appealing. I
> > know of RB's libcsp, but have been slightly put off just
> > because it seems very old now and wonder how "supported" it is.
> > Finally, in a mail to a developer here I wrote:
> > /"RIC: Finally, it is interesting to note that cooperative
> > scheduling is
> > *very* much more efficient than preemptive scheduling; the
> > trick is to write the scheduling points into the code using
> > the compiler, making it less likely that one thread starves others."/
> > /"AJCD: //Also, cooperative scheduling ultimately relies on
> > state machines, which are hard to debug and maintain, and
> > tend to rely more on heap allocation than stack allocation."/
> > Now, I don't think AJCD's point about state machines is quite
> > valid in this context as I think he's thinking about big
> > switch statements of bits of code and a loop, but he's an
> > intelligent guy: any thoughts on a good reply?
> > Going back to my comment, are there any C compilers that
> > have/can be "instrumented" to do the "inject-scheduling
> > point" thing, with suitable library support. All I can think
> > of is Handel-C, which is not appropriate.
> > Thanks, and Merry Christmas to you all!
> > Ruth