🚀 go-pugleaf

Johan Compagner <joco@wxs.nl> wrote in message
news:7tusb2$pmu$1@news.software.ibm.com...

> But is it really a problem?
> If you compile your code later with a jdk1.2 compiler then
> it shows up and you must change some import statements.
> VAJ (java2) makes it very easy to detect because of its incremental
> nature. You are right of course that you can better beat the problem
> before it is there.

It's mainly a problem when other people compile, or if you haven't
worked on the code for a while and then compile under Java2.

Figuring out the resolution can be tricky if it's not your code or not
fresh in your memory.

> Enrique's post was about compiling with 1.1 and running it under 1.2

true -- this is a compilation issue.

> P.S.
> do you have tested Swing1.1.1? Because IBM should!!

A bit -- haven't had much time. We need to do something with the
BeanInfos so we can set preferred features. With just .class files we
can't do it.

> A complete clean install of 3.0beta i couldn't get swing1.1.1 added
first
> to the workspace: corruption all the time. I tried several times.

Worked first time for me...


--
-- Scott

=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Scott Stanchfield    thetick@jguru.com    http://www.jGuru.com/thetick
jGuru Training by MageLang Institute      http://www.jGuru.com
VisualAge for Java Tips --> http://www.jGuru.com/thetick/visualage/tips
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=