Re: GeneralPath 1.6 backward compatibility?
zorci@epost.de wrote:
...For development I would need to set the
bootclasspath for eclipse3.2 (auto-build javac, not called with ant)
but I dont know where to set this param.
...do you realise how pathetic that sounds?!
Eclipse eats up ant build files, and yet you
are telling me you cannot write an ant script
for building? Cannot find the setting in your
IDE? Cannot change to an IDE where you
...have the control/know what you're doing?
(shrugs) My best suggestion if an IDE 'has you
by the short and curlies' is to dump the IDE.
...While testing I found that
setting the compiler compliance level to "1.4"
What does that translate to? What javac options
are being set there? -source?* -target?*
..seems
Seems? You do not sound very convinced.
....also to work for my purpose (level 1.3 didn't).
* But that sort of compromise, has been seen
in the past to be insufficient to guarantee that
code compiled by later JVM's is capable of
being run on earlier ones.
The problem is that although all 'externally
visible' methods and classes might be
compatible with the earlier versions, and
the class format is compatible with the
earlier version, the compiler might use
'shortcuts' available within the later VM,
inside methods designed to run on
earlier versions.
To *guarantee* compatibility with an earlier,
the code *must* be compiled against an rt.jar
of that version.
Andrew T.