[3208] in java-interest

home help back first fref pref prev next nref lref last post

Re: Ordering semantics of runtime exceptions

daemon@ATHENA.MIT.EDU (Arthur van Hoff)
Thu Nov 2 23:19:17 1995

Date: Thu, 2 Nov 1995 17:58:57 -0800
From: Arthur.Vanhoff@Eng.Sun.COM (Arthur van Hoff)
To: jeremy@suede.sw.oz.au
Cc: java-interest@java.Eng.Sun.COM


Hi Jeremy,

> > > (except perhaps for "threadsafe" class members).
> > 
> > We no longer have threadsafe class members. We've gone back to volatile...
> 
> Ah, really.  Does that mean its never correct to optimise memory access
> to a class member?  Or do you mean that there's a "volatile" keyword
> and members have to be explicitly declared as such?

The latter. More optimizations are now possible, we chose the wrong
default and made everything volatile. Now it back to everything being
threadsafe, and you have declare variables to be volatile. Makes more sense.

Have fun,

	Arthur van Hoff
-
This message was sent to the java-interest mailing list
Info: send 'help' to java-interest-request@java.sun.com

home help back first fref pref prev next nref lref last post