| 1. | This is accomplished by obtaining a mutual - exclusion lock for a given object for the duration of the code block
这是通过在代码块运行期间为给定对象获取互斥锁来实现的。 |
| 2. | Be sure to read the next installment in the series , " migrate your apps from os 2 to linux : part 3 . timer and dll calls
将应用程序从os / 2迁移到linux上：第1部分，线程、互斥锁和信号量 |
| 3. | Keyword marks a statement block as a critical section by obtaining the mutual - exclusion lock for a given object , executing a statement , and then releasing the lock
关键字将语句块标记为临界区，方法是获取给定对象的互斥锁，执行语句，然后释放该锁。 |
| 4. | Keyword enforces a mutex mutual exclusion that prevents more than one thread at a time from entering a synchronized block protected by a given monitor
关键字强制实施一个互斥锁（互相排斥） ，这个互斥锁防止每次有多个线程进入一个给定监控器所保护的同步语句块。 |
| 5. | Additionally , for the concurrent problem during them design process , we proposed a novel multi - versioning approach and also developed a locking combination for this method
并且针对图案协同设计中存在的一致性维护和冲突问题，探讨了一致性维护的多版本方法和基于多版本方法的立即互斥锁的实现。 |
| 6. | Features like process - shared mutexes are also available on linux , and thus the solaris code related to ipc mechanisms using pthread mutex locks and condition variable can be used on linux
在linux上还可以利用一些新特性，例如进程共享互斥锁，因此solaris中使用pthread互斥锁和条件变量的那些有关ipc机制的代码在linux中都可以使用。 |
| 7. | Of this series covered threads and synchronization mechanisms like semaphores and mutexes . this second installment looks closely at memory management , various ipc mechanisms including shared memory and pipes , and file management
介绍了线程以及一些同步机制，例如信号量和互斥锁；这第2期文章着重介绍内存管理、文件管理和几种ipc机制，包括共享内存和管道。 |
| 8. | While writes to volatile variables are guaranteed to be immediately visible to other threads , there is no way to render a read - modify - write sequence of operations atomic , meaning , for example , that a volatile variable cannot be used to reliably implement a mutex mutual exclusion lock or a counter
虽然可以保证其他变量可以立即看到对可变变量的写入，但无法呈现原子操作的读-修改-写顺序，这意味着（比如说）可变变量无法用来可靠地实现互斥（互斥锁定）或计数器。 |
