Concurrency Nomenclature

Started by
10 comments, last by Fruny 19 years, 6 months ago
Thanks. Looks like both CriticalSections and mutexes both do exactly what I want them to. I'll probably go with CriticalSections as I'm only using one process and since this is part of an API, efficiency is always a consideration as it is unclear how often the user may use any functions.

Looked up spinlocks. They could possibly work but the idea of using a busy/waiting loop just spins me the wrong way. And monitors seem a bit too bulky, but thanks for the ideas.
Advertisement
My multithreaded programming book calls that a recursive mutex.
"Debugging is twice as hard as writing the code in the first place. Therefore, if you write the code as cleverly as possible, you are, by definition, not smart enough to debug it." — Brian W. Kernighan

This topic is closed to new replies.

Advertisement