Subject:
|
Re: Very strange problems
|
Newsgroups:
|
lugnet.robotics.rcx.legos
|
Date:
|
Sun, 21 May 2000 19:33:19 GMT
|
Viewed:
|
1455 times
|
| |
|
|
On Sun, 21 May 2000, Luis Villa wrote:
> Just that it is not pre-emptive. If you don't msleep() at the appropriate
> places in your code, you'll never go back to the scheduler or the other
> threads. This can come as a surprise, since you'll only notice it when
> one thread never executes.
> Luis
Ack! I knew that it was cooperative in the 0.1.x series, but I had thought
it was preemptive in 0.2.x. Drat. Well, I don't think it's a major problem
for me, since I call msleep() religiously, but it's something to look
into. Thanks.
--
"Our doubts are traitors, and make us lose the good we oft might win by
fearing to attempt." - William Shakespeare
Mike Ash - <http://www.mikeash.com/>, <mailto:mail@mikeash.com>
|
|
Message has 1 Reply:
 | | Re: Very strange problems
|
| (...) I have not done large-scale "production" work with 0.2.x, really, so I may be vastly incorrect. Ah-hah. The legOS homepage (at least) indicates that you are correct. My fault for scaring people... sorry. Luis ---...--- "Going to California (...) (25 years ago, 21-May-00, to lugnet.robotics.rcx.legos)
|
Message is in Reply To:
| | Re: Very strange problems
|
| (...) Just that it is not pre-emptive. If you don't msleep() at the appropriate places in your code, you'll never go back to the scheduler or the other threads. This can come as a surprise, since you'll only notice it when one thread never executes. (...) (25 years ago, 21-May-00, to lugnet.robotics.rcx.legos)
|
20 Messages in This Thread:
  
- Entire Thread on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
This Message and its Replies on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
|
|
|
|
