Re: immutable BigInteger

• Subject: Re: immutable BigInteger
• From: Doug Zwick <email@hidden>
• Date: Tue, 16 Oct 2007 14:30:07 -0600
• Delivered-to: email@hidden
• Delivered-to: email@hidden

Doug Zwick wrote:

Eduard de Jong wrote:

However, one key point i tried to make, which i'm not sure has come
across as clear as i wished, is that there is no choice in being
thread safe or not:

A program that is not thread safe is an INCORRECT program. Whatever
speed&memory performance gain it has it still is a broken program, it
CAN FAIL AT ANY TIME.

This statement is certainly true, however it does not follow that *any* program making use of a class (or other piece of software) that is not MT-safe becomes MT-safe.

How the non-safe software is used is important. Serializing access to non-safe code through a single thread is a valid technique for creating MT-safe software, and is commonly used.

_______________________________________________
Do not post admin requests to the list. They will be ignored.
Java-dev mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/java-dev/email@hidden

• Prev by Date: RE: Apple took Java 1.6 away...
• Next by Date: Re: Apple took Java 1.6 away...
• Previous by thread: Re: immutable BigInteger
• Next by thread: Programming iTunes
• Index(es):
  • Date
  • Thread