You are confused a bit. All code runs in some thread, yet the class that defines this code needs not extend Thread. If this were not so, all classes had to extend Thread or you couldn’t call any of their methods. Look at the following analogy: public class Test { public static void main(String[] args) … Read more
The correct (standard) way to do this on C and Windows is with __beginthreadex. This is usually preferred to calling CreateThread directly as CreateThread doesn’t init C runtime support for the thread. So if you create a thread using CreateThread, and call a CRT function, bad stuff can/will happen. Note that __beginthreadex calls CreateThread internally, … Read more
In onStop() method, call interrupt as follows: yourThreadObject.interrupt() and in the run() method of the thread, have a condition that checks for Thread’s interrupt status. Depending on your implementation, you might want to enclose this check within a while loop as, public void run() { while (!Thread.interrupted()) { //do something … } } or you … Read more
Is atoi multithread safe? Yes, in the linux man page of atoi() it is written: ┌────────────────────────┬───────────────┬────────────────┐ │Interface │ Attribute │ Value │ ├────────────────────────┼───────────────┼────────────────┤ │atoi(), atol(), atoll() │ Thread safety │ MT-Safe locale │ └────────────────────────┴───────────────┴────────────────┘ So it’s just using the variables you pass from your thread (locale) and is completely thread-safe (MT-Safe), as long as you … Read more
As a general rule, it’s more flexible to leave it to the user. For example, consider a map-type container. Suppose the application needs to atomically move something from one map to another map. In this case, the user needs to lock both maps before the insert-erase sequence. Having such a scenario be automatically taken care … Read more