 | | Re: Implementation of Installable Timers
|
|
(...) You are right. I found in an app that I was using that if I pressed the run / stop button, my task would be killed, and leave a dangling timer - which would usually blow the little brick into the weeds :o) I 'solved' it in a crude way by (...) (20 years ago, 9-Jan-04, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Implementation of Installable Timers
|
|
Iain McInnes wrote: [snip] (...) Great idea! (...) In your implementation, would it be possible for the client task to be killed (in the case of a run-away task)... causing the struct to be deallocated... while the struct is still in the linked (...) (20 years ago, 8-Jan-04, to lugnet.robotics.rcx, lugnet.robotics.rcx.legos)
|
| |
| | Points to: 'Implementation of Installable Timers'
|
|
Hi, ppl. I posted this one in the wrong place :0 (URL) Enjoy ! Iain. (20 years ago, 8-Jan-04, to lugnet.robotics.rcx.legos)
|
| |
| | Points to 'Design by Contract'
|
|
Hi, Folks, I posted some stuff on an assert() macro - in the wrong place - (D'oH). The thread is here: (URL) Enjoy ! Iain. (20 years ago, 8-Jan-04, to lugnet.robotics.rcx.legos)
|
| |
| | Hello World !
|
|
Hello everybody. I’ve been fooling around with BrickOS in the last few weeks, becoming familiar with it. BrickOS is very cool. Thank you, those who have made it what it is, and thank you, those who help out those with the common problems (yes, I had (...) (20 years ago, 8-Jan-04, to lugnet.robotics.rcx.legos)
|
