可以以两种方式设置互斥的类型。
这些选项并不是互斥的。
概览模式和聚焦模式是互斥的。
这里是创建互斥的示例代码(见下面的6和7)。
Here's the sample code for creating a mutex (see Listings 6 and 7 below).
只有能访问源代码的人才可能知道这种互斥的情况。
Only those with access to the source code will know about the mutually exclusive arrangement.
在厕所里重要的例子二进制信号量互斥的区别？
Difference between Binary Semaphore and Mutex in the toilet key example?
下面是关于一个非常好的文章互斥的解决方案。
在进程的生命周期内，可能会经历一系列互斥的状态。
During its lifetime, a process may go through a set of mutually exclusive states.
高质量的教学和研究并不互斥，但它们也不是“天生一对”。
Good teaching and research are not exclusive, but they are also not automatic companions.
还要注意，两个条件变量使用相同的互斥锁。
如果可能，在设计程序时决不要锁定一个已经锁定的互斥量。
If possible, just design your program never to re-lock a mutex it already has.
任何对一组事件的访问都由一个互斥对象来保护。
Any access to a collection of events is guarded by a mutual exclusion object.
表现互斥现象的数据结构，也被当作二元信号灯。
A data structure for mutual exclusion, also known as a binary semaphore.
增强的命令不需要像以前的方法一样使用互斥型锁。
The enhanced commands do not require an exclusive lock like previous methods.
如果放置了过少的互斥对象，代码将出现奇怪和令人尴尬的错误。
If you place too few, your code will have weird and embarrassing bugs.
基于互斥锁的方法的问题。
最后，可以通过调用mutex_is_locked检查互斥锁的状态。
Finally, you can check the status of a mutex through a call to mutex_is_locked.
比如，多线程的每一个线程可以有一个互斥锁的句柄。
For example, multiple threads can each have a handle to a mutex object.
那就意味着给请求加一个互斥是无用的开销。
That means that wrapping a mutex around the request is useless overhead.
在这个模型中，所有被唤醒的任务都不持有互斥锁。
灾害互斥链是四种灾害链中的一种。
Incompatibl chain of disasters is one of four disaster chains.
灾害互斥链是四种灾害链中的一种。
Incompatibl chain of disasters is one of four disaster chains.
应用推荐