This is the mail archive of the
java@gcc.gnu.org
mailing list for the Java project.
Re: assertion support
- From: Tom Tromey <tromey at redhat dot com>
- To: jmr at ugcs dot caltech dot edu (Jesse Rosenstock)
- Cc: java at gcc dot gnu dot org
- Date: 12 Aug 2002 11:37:58 -0600
- Subject: Re: assertion support
- References: <20020803220734.4829A84053@euro.ugcs.caltech.edu>
- Reply-to: tromey at redhat dot com
>>>>> "Jesse" == Jesse Rosenstock <jmr@ugcs.caltech.edu> writes:
Jesse> I see Bug 6996 (gij needs assertion-related command-line
Jesse> options). I have a patch that adds command line options for
Jesse> controlling assertion status to gij.
Jesse> Is this what the bug had in mind, or something more
Jesse> sophisticated such as optimizing the byte code at load time if
Jesse> $assertionsDisabled is true?
Basically what we want is to duplicate the command-line processing of
the JDK. If your patch does that, then that is sufficient. I hadn't
even considered optimizing the bytecode at load time...
Jesse> Also, what about support in gcj? Would it make sense to be
Jesse> able to set defaults at compile time, which could be changed at
Jesse> runtime by a GCJ_ASSERTION_STATUS environment variable?
Yes, adding an option to gcj to allow assertions to be disabled at
compile-time would be nice. I'm not so sure about the environment
variable though.
Tom