But PVM doesn't support thread safety.
但是PV M不支持安全的线程机制。
Use the concurrent collections if you want to ensure thread safety.
使用并发集合，如果你想确保线程安全。
Doug Cutting has posted on the topic of thread safety a couple of times.
Doug Cutting曾几次发表线程安全性的主题。
Intrusive containers have thread safety guarantees similar to STL containers.
介入式容器具有与STL容器相似的线程安全性保证。
Any time you access a VCL UI component, you need to implement some type of thread safety measure.
任何时候你访问VCLUI组件时，您需要实现某种类型的线程安全措施。
Consider a thread-safe container class - a data structure that guarantees thread safety to its clients.
可以考虑使用一个线程安全容器类—一个保证用户操作线程安全的数据结构。
In general, strive to make your synchronized blocks as lean as possible, without harming thread safety.
一般而言，在保证线程安全的前提下要尽可能地简化同步语句。
In some scenarios, this can result in a big win that outweighs the cost of the extra thread safety work.
在某些情况下，这会大大提高性能，即使在线程安全性上有额外的开销。
You need to do some thread safety work and make sure that UI modifying code gets sent to the main thread.
你需要做一些线程安全工作，确保UI修改代码被发送到主线程。
The set-after-write technique may be useful for state replication, but it is not enough to provide thread safety.
set-after-write技巧可能对状态复制非常有用，但还不能提供线程安全。
MFC provides a number of classes that allow threads to synchronize access to objects to maintain thread safety.
MFC提供许多类别，这些类别允许执行绪同步物件的存取，以维护执行绪安全性。
Specifically, thread safety is about properly coordinating access to mutable data that is accessed by multiple threads.
具体来说，线程安全是指适当地协调对被多个线程访问的可变数据的访问。
Unfortunately, thread safety is not an all - or - nothing proposition, and it is surprisingly difficult to define.
不幸的是，线程安全并不是一个非真即假的命题，它的定义出人意料的困难。
Sequel provides thread safety, connection pooling and a concise DSL for constructing database queries and table schemas.
Sequel具有线程安全，连接池等特性，同时提供了简洁的DSL用来创建数据库查询以及表方案。
Static class methods may support a different level of thread safety than those associated with an instance of that class.
和实例的方法相比，静态类的方法或多或少拥有更高的线程安全性。
Object for the duration of the iteration. as the above example shows, thread safety is not all - or - nothing. the methods of.
如上面的例子所示，线程安全性不是一个非真即假的命题。
At the same time, it is insufficient to provide true thread safety, in that many common compound operations still require additional synchronization.
同时，这样仍不足以提供真正的线程安全性，许多公用的混合操作仍然需要额外的同步。
The Participant pattern lets you make the transition from simple aspects to more complex ones such as those for transaction management, thread safety, security, etc.
Participant模式可以将简单的方面转换为更复杂的方面，如负责事务管理、线程安全、安全性等方面。
The mapping is difficult to use and contains many pitfalls that lead to bugs, particularly with respect to thread safety, exception safety, and memory management.
映射不易使用，包含许多导致bug的缺陷，特别关于线程安全性、异常安全性和内存管理的部分。
The ConcurrentHashMap implementation, along with the rest of util.concurrent, has been extensively peer-reviewed by concurrency experts for correctness and thread safety.
ConcurrentHashMap实现，加上ut il . concurrent包的其他部分，已经被研究正确性和线程安全性的并发专家所正视。
As soon as you implement a nontrivial class maintaining state between method calls, consumers of the class will want to know details about thread safety and performance.
一旦您实现了在方法调用之间保持状态的重要类，该类的使用者就会希望了解有关线程安全和性能的详细信息。
To guarantee thread safety during enumeration, you can either lock the collection during the entire enumeration or catch the exceptions resulting from changes made by other threads.
若要确保枚举过程中的线程安全性，可以在整个枚举期间锁定集合，或者捕获由其他线程进行的更改所导致的异常。
To guarantee thread safety during enumeration, you can either lock the collection during the entire enumeration or catch the exceptions that result from changes made by other threads.
若要保证列举期间的安全执行绪，您可以在整个列举期间锁定集合，或拦截由其他执行绪所做变更造成的例外状况。
Analyzing the thread safety of a program that USES containers is harder with intrusive containers, because the container might be modified indirectly without an explicit call to a container member.
分析一个使用容器的程序的线程安全要比分析介入式容器更困难，因为可以无需显式调用容器的成员函数就间接修改该容器。
No table-wide locking is needed (or even possible) to provide thread-safety when iterating the collection.
在对集合进行迭代时，不需要表范围的锁就能提供线程安全性。
It is easy to "forget" this rule, especially when reading — but doing so creates numerous risks for the thread-safety of your program.
很容易“忘记”这个规则，特别是在读取时——但是这么做可以造成很多有关程序线程安全的风险。
We don't declare any variables that might cause thread-safety issues.
我们没有定义任何会引起线程安全问题的变量。
On MVM side, we don't need to care about thread-safety, but VM communications.
从MVM的角度来看，我们不需要关注线程安全，但是需要考虑VM通讯。
Not only must you pay attention to thread-safety issues, but you need to remember that a listener can mess things up for its caller in other ways, too.
不仅要注意线程安全问题，还需要记住：侦听器也可以用其他方式为它的调用者把事情搞糟。
Not only must you pay attention to thread-safety issues, but you need to remember that a listener can mess things up for its caller in other ways, too.
不仅要注意线程安全问题，还需要记住：侦听器也可以用其他方式为它的调用者把事情搞糟。
应用推荐