Subject:
|
Announce: NQCIPC update
|
Newsgroups:
|
lugnet.robotics
|
Date:
|
Fri, 29 Oct 1999 00:46:23 GMT
|
Original-From:
|
Brian Connors <connorbd@yahoo!IHateSpam!.com>
|
Viewed:
|
802 times
|
| |
|
|
As some of you may know, about three weeks ago I
released a package called NQCIPC that provides a basic
API for semaphores and intertask messaging on NQC.
Originally written for NQC 1.x, it's been updated for
2.x and I'd be interested in seeing what all of you
think of it. I'd especially be interested in feature
suggestions (if practical); I'd also like a better
name than NQCIPC if someone has an idea (anyone like
Spectre (by analogy with spirit.ocx)?).
The home page is
http://www.geocities.com/ResearchTriangle/Station/2266/nqcipc/nqcipcdoc.html
and it contains everything relevant to the package.
Check it out and let me know what y'all think.
Brian Connors
=====
--
|
|
Message has 2 Replies:
 | | Re: Announce: NQCIPC update
|
| Brian, this looks very useful; I'll try it out soon! NQCIPC made perfect sense to me, but I have had my Nerd Merit Badge for a long time. People who have never done anything with multitasking before will not recognize other related words like (...) (25 years ago, 29-Oct-99, to lugnet.robotics)
| | | bug in semaphore code (was Re: Announce: NQCIPC update
|
| Your semaphore acquire algorithm isn't too good. Here is your code: #define sem_acquire(s) until (s == 0); s = 1; If two tasks are waiting for the semaphore at the same time, it is quite likely that both will get it: // (s is currently nonzero) task (...) (25 years ago, 29-Oct-99, to lugnet.robotics)
|
6 Messages in This Thread:
 
 
- Entire Thread on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
|
|
|
|
