Re: JavaMemoryModel: final, pseudo-final and write protectedfields

From: Joseph Bowbeer (jozart@csi.com)
Date: Tue Oct 26 1999 - 16:16:33 EDT

Speaking of System's setErr and setOut methods, I hear that a recent JDC
(developer.java.sun.com) mailing contains sample code.

I can try to track it down if anyone's interested, but I think it boils down
to something like the following:

    PrintStream out = System.out;
    PrintStream log /* = output log */;
    System.out.println("before logging");
    System.setOut(log);
    System.out.println("logging");
    System.setOut(out);
    System.out.println("after logging");

Is there anything in the old JMM or new JMM to prevent the compiler from
emitting code that reads System.out only once? 

--
Joe Bowbeer

----- Original Message -----
From: Bill Pugh <pugh@cs.umd.edu>
To: <javaMemoryModel@cs.umd.edu>
Sent: Thursday, October 21, 1999 1:19 PM
Subject: re: JavaMemoryModel: final, pseudo-final and write protectedfields

> I haven't been able to find any code that actually invokes the setIn,
> setOut and setErr functions, so I don't have a feeling for how
> important that is. One suggestion would be to deprecate those
> functions, and see who squeals.
>

-------------------------------
JavaMemoryModel mailing list - http://www.cs.umd.edu/~pugh/java/memoryModel

This archive was generated by hypermail 2b29 : Thu Oct 13 2005 - 07:00:21 EDT