Multithreading programming requires attention to thread safety issues.

多线程编程需要注意线程安全问题。

But PVM doesn't support thread safety.

但是PVM不支持安全的线程机制。

For details on thread-safety and race conditions, see Thread-Safe Components.

如需执行绪安全性和竞争情形的详细资讯，请参阅安全执行绪的元件。

Intrusive containers have thread safety guarantees similar to STL containers.

介入式容器具有与STL容器相似的线程安全性保证.

In situations where you know you need thread safety, use a thread-safe view.

在需要线程安全的情况下，请使用线程安全视图。

Doug Cutting has posted on the topic of thread safety a couple of times.

Doug Cutting 曾几次发表线程安全性的主题。

Running some of the threads need to share data, So each thread must consider other with it to share the data with the state of the thread, This is the thread safety.

一些同时运行的线程需要共享数据，因此每个线程就必须要考虑其它与它一起共享数据的线程的状态与行为，这就是线程安全的问题。

On MVM side, we don't need to care about thread-safety, but VM communications.

从MVM的角度 来看，我们不需要关注线程安全，但是需要考虑VM通讯。

Inserting an object in containers that will be modified by different threads has no thread safety guarantee, although in most platforms it will be thread-safe without locking.

向一个会被其它线程修改的容器插入对象是没有线程安全性保证的，虽然在多数平台上，它是无锁定线程安全的。

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.

不仅要注意线程安全问题，还需要记住：侦听器也可以用其他方式为它的调用者把事情搞糟。