 | | LeJos threads / sleep() takes too long —Bart Pattyn
| | | | Experimenting with Lejos, two 'major' problems: memory (cleaning up platform & lang: Math.class is huge!) and... threads. I have the impression my "try { sleep(nnn) }" takes a somewhat arbitrary time. It's 'at least' nnn milisec, but often much (...) (23 years ago, 6-Mar-02, to lugnet.robotics.rcx.java)
| | | | | | | | | | Re: LeJos threads / sleep() takes too long —Juergen Stuber
| | | | | Hi Bart, (...) if you mean LISTENER_THREAD then that sounds plausible. (...) Yes, LISTENER_THREAD has maximum priority, so it runs before any threads of lower priority, even yield doesn't help. (...) Yes, I think we'll have to fix that somehow. (...) (23 years ago, 6-Mar-02, to lugnet.robotics.rcx.java)
| | | | | | | | | | | | Re: LeJos threads / sleep() takes too long —Paul Andrews
| | | | | The priority mechanism used in lejos is the same as that specified in the Real Time Specification for Java (RTSJ): Threads of a higher priority will absolutely block threads of a lower priority as long as they remain runnable. The sensor listener (...) (23 years ago, 1-Apr-02, to lugnet.robotics.rcx.java)
| | | | | | |
