|
|
 | | Re: stop task
|
| (...) It hasn't, Elizabeth - I'm not upset at John, and he knows *far* more about programming than I do. I just wanted to point out that there are process where abruptly "killing" a thread was one of the best solutions I ever found, due to the speed (...) (17 years ago, 25-Jul-07, to lugnet.robotics.nxt)
| | | | | RE: stop task
|
| Everyone, Being fair in the judgement in using a global watchdog flag to terminate a task. Honestly, when I have a multi-threaded process, I have always used a watchdog type of flag, mutex, semaphore, etc. to signal a thread to terminate. I hardly (...) (17 years ago, 25-Jul-07, to lugnet.robotics.nxt)
| | | | | Re: stop task
|
| (...) Well, you may not consider that awkward, but having been able to use the "stop" & "start" task commands in NQC, I do actually consider it very awkward. For instance, if I want to immediately stop some task under the "stock" FW... well, I (...) (17 years ago, 24-Jul-07, to lugnet.robotics.nxt)
| | | | | Re: stop task
|
| (...) It is not a rather awkward option, imho. That's like saying breaking out of an infinite loop using a flag is awkward and that it would be better to have some form of stop loop keyword that you could use from outside the loop instead. Is it (...) (17 years ago, 24-Jul-07, to lugnet.robotics.nxt)
| | | | | Re: stop task
|
| (...) Using a global to flag out of a task is about the only (rather awkward) option I know of. This is one of the things that I really have issues with under the NXT-G FW. (17 years ago, 24-Jul-07, to lugnet.robotics.nxt)
|
|
