It will be bad news for JMM if the Realtime Java spec (RTSJ) is adopted in its
current form before JMM gets off the ground.
According to your schedule, the JMM JSR won't be announced until a month or
two *after* public review of RTSJ has closed. I urge everyone to checkout RTSJ
while public review is still open.
The following article in Dr. Dobb's Journal presents a good overview of RTSJ.
It's also been the only place I've been able to find code samples.
The are four code samples in the article, and not a single 'synchronized'
This quote is from section 5.2 of RTSJ (rev. 0.90):
"Java monitors, and especially the synchronized keyword, provide a very
elegant means for mutual exclusion synchronization."
There is no mention of using 'synchronized' to transmit values between
-- Joe Bowbeer
----- Original Message ----- From: "William Pugh" <email@example.com> To: <javaMemoryModel@cs.umd.edu> Sent: Wednesday, January 19, 2000 6:02 AM Subject: JavaMemoryModel: Schedule for changing the Java Memory Model
> > I talked with Tim Lindholm, and we thought that the following schedule > would be reasonable for changing the Java Spec: > > * April - Announce a JSR to change the spec. This would set out the issues > and point to > some specific proposals. > * June - BOF's at JavaOne and PLDI, form expert committee, start process > * Summer - provide guidance on changes needed to JVM's and libraries to > make them > compatible with the spec > * By end of 2000 (earlier if possible) - finalize spec > > This schedule is ambitious schedule, but I think this is too important to > let it slip any further than this. > > What do other people think of this schedule? > > Bill > > ------------------------------- > JavaMemoryModel mailing list - http://www.cs.umd.edu/~pugh/java/memoryModel
------------------------------- JavaMemoryModel mailing list - http://www.cs.umd.edu/~pugh/java/memoryModel
This archive was generated by hypermail 2b29 : Thu Oct 13 2005 - 07:00:24 EDT