Re: A java DEBUG flag

[Kevin A. Burton]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Mark Wielaard <address@hidden> writes:

<snip>

> Does it has to be a compile time constansts?
> I would like to be able to have a class library where I could selectively
> turn on/off some debugging code at runtime. If we used something like
> System.getProperty("gnu.java.io.serialisation.debugging") to set these
> constants (you can even do that in an interface) then at runtime the
> user could do a -Dgnu.java.io.serialisation.debugging=yes to turn on
> the debugging. (It should at least be an option to have these 'constants'
> compiled in so they can be set dynamicly at runtime IMHO.)

SUN has a JSR for JDK 1.4 (Merlin) for assertions.  Basically you can:

assert i > 4;

And then prior at runtime you can turn this off... I would say any
implementation of this should use the JSR for a spec.  I read it and although at
first I didn't like it... I came around and now think it is the best.

As an asside... I have always wanted a standard place to read java properties
files instead of having to pass -D to the JVM.  Maybe we need to have an
/etc/java.properties file that GJC has to read.  Since -D won't work for
statically compiled apps in GJC maybe this is the better way.

Kevin

- -- 
Kevin A. Burton ( address@hidden, address@hidden, address@hidden )
             Cell: 408-910-6145 URL: http://relativity.yi.org

proprietary == evil
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.4 (GNU/Linux)
Comment: Get my public key at: http://relativity.yi.org/pgpkey.txt

iD8DBQE6HeQgAwM6xb2dfE0RAnuzAJ4lWvcpBx2FNPg7CYRHd3/YNX1YEACeMTfM
HHXImBMHweABt3FrXcb/Rvc=
=WYmK
-----END PGP SIGNATURE-----



cracking Clinton Peking BATF $400 million in gold bullion arrangements PLO
strategic Cocaine assassination Mossad Marxist South Africa Legion of Doom DES