ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jon Skeet" <>
Subject RE: Why stop at JDK1.2? Only semi-serious question...
Date Mon, 15 Jul 2002 17:31:07 GMT
> Maybe it's a hack, but surely no worse than:
> #ifdef RELEASE
> #define ASSERT(fact)
> #else
> #define ASSERT(fact) _assert(fact,_FILE_,_LINE _)
> #endif

No, no worse than that - but that's bad enough.
> As far as using BCEL, sure... But at install time or runtime? 
> If at runtime, what's the overhead?

Once per class loading. I would imagine it'll be hard to even detect, unless BCEL's slower
than I'd guess.

> And leaving the asserts in the bytecode doesn't enable
> them: One still needs -ea on the Java command line (or 
> similar construct programmically), maybe restricting the assertions in 
> actual Ant code (restricted to packages).

Sure - but it means you *can* enable them without recompiling, which is the important thing
as far as I'm concerned.


To unsubscribe, e-mail:   <>
For additional commands, e-mail: <>

View raw message