[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: A java DEBUG flag
From: |
Bryce McKinlay |
Subject: |
Re: A java DEBUG flag |
Date: |
Sat, 25 Nov 2000 11:33:22 +1300 |
Mark Wielaard wrote:
> > Granted, a smart JIT will be able to take advantage
> > of it being a final field and eliminate the debug code from what it
> > generates. However, if it is used extensively in the runtime then it is
> > probable that the flag would be evaluated before the system property is set,
> > making it useless.
> So you have to reevaluate the System property every time (as you seem to
> do in your ObjectInputStream patch). I was hoping that you could set system
> properties on the command line with gcj compiled binaries then you could
> be sure that such a property was always set (or not set). This is what
> gij seems to do.
Setting a property on the command line doesn't stop the application changing
that
property later. I figured it would be nice to be able to disable debugging at
runtime as well, hence the re-checking the property in the ObjectInputStream
constructor.
regards
[ bryce ]
Re: A java DEBUG flag, Mark Wielaard, 2000/11/23
Re: A java DEBUG flag, Kevin A. Burton, 2000/11/24
RE: A java DEBUG flag, Boehm, Hans, 2000/11/29
RE: A java DEBUG flag, Boehm, Hans, 2000/11/29
Re: A java DEBUG flag, Brian Jones, 2000/11/29
Re: A java DEBUG flag, Nic Ferrier, 2000/11/29
Re: A java DEBUG flag, Patrick Tullmann, 2000/11/29
Re: A java DEBUG flag, Nic Ferrier, 2000/11/30