4 ms·
I never understood why semaphore was called a primitive until I've read the original paper. Dijkstra called semaphore a primitive because the controlling part w
by Mikhail_Edoshin 4y ago
I never understood why semaphore was called a primitive until I've read the original paper. Dijkstra called semaphore a primitive because the controlling part was a mere integer. A Boolean would be even more primitive but probably insufficient. But since a semaphore also has a queue of waiting processes it is of course a rather complex system.
- kazinator 4y agoIf you have that complex scheduling mechanism with queues and all, about the dumbest thing you can do is build a semaphore with it ... and then use the semaphore to build other primitives.