|
From: | Eric Blake |
Subject: | Re: [Jikes] Bug with -target option |
Date: | Tue, 03 Dec 2002 14:08:43 -0700 |
User-agent: | Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.0.1) Gecko/20020823 Netscape/7.0 |
Brian Jones wrote:
I didn't set the source option. It is just a HelloWorld program, really, so it doesn't use assertions ;) Should I try setting the source too, i.e. does source default to 1.4 ? My guess would be that it's easy to compile 1.1 source for a 1.4 target, but not the other way around, so that might explain the problem I'm seeing. I'll check and post a reply tonight.Setting the source option to 1.2 solved my problem.I think Classpath sets the -target in lib/Makefile.am for jikes compiles to 1.1 without setting the -source option. Should something be changed then? The point was mainly to make emitted class files useful to 1.1+ JVMs.
I have just recently changed the behavior of -source and -target in the CVS version of jikes (post 1.18). Before, if you set -target, you could not parse assert. But now, -source and -target are sufficiently independent. With the addition of the new command-line option --noassert, you may compile code with assert statements while still emitting code workarounds necessary for running on 1.1 JVMs.
For now, jikes 1.18 and CVS jikes default to -source 1.3 and -target 1.3 if neither is specified, to be drop-in compatible with the behavior of javac in JDK 1.4.1_01.
-- This signature intentionally left boring. Eric Blake address@hidden BYU student, free software programmer
[Prev in Thread] | Current Thread | [Next in Thread] |