[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: A java DEBUG flag

From: Mark Wielaard
Subject: Re: A java DEBUG flag
Date: Fri, 24 Nov 2000 09:33:02 +0100
User-agent: Mutt/1.2.5i


On Fri, Nov 24, 2000 at 12:19:07PM +1300, Bryce McKinlay wrote:
> Mark Wielaard wrote:
> > If we used something like
> > System.getProperty("") to set these
> > constants (you can even do that in an interface)
> I don't think so ;-)

What don't you think so?
What I meant was something like the following:

interface I {
> > then at runtime the
> > user could do a 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.)
> We'll do that as well. To get the debug output you'll have to configure with
> "--enable-libgcj-debug" _and_ set the runtime property. But we do want to
> have the compile time constants in order to ensure there is _no_ overhead
> from the debugging code for an optimized build.

OK that is fair. But I would really like to see a solution that generated
a interface like I did above so that you could dynamicly turn it on and
a compile time configuration option to turn the above interface into

interface I {
    boolean SERIALISATION_DEBUG = false;

But I think the default should be that you can dynamicly turn the debugging
code on.



reply via email to

[Prev in Thread] Current Thread [Next in Thread]