| |
| |
| |
|
Page: 1 2
Comments:
<0> besides 1.3 is far behind in performance and functionality/language features
<1> yeah, but they are making simple games, that they want their friends to play, its a bummer when there friends are like "what it doesnt loaD? piece of crap..." you know?
<1> know everyone has jre1.5
<1> not
<0> and how does using 1.3 help there ?
<1> well if the audience has jre1.5 it will play right?
<1> i mean 1.3
<0> yes
<0> no
<1> if you compile under jdk 1.3, then it will play under jre 1.3
<0> if a student writes a game in 1.5 it will not run on 1.3
<1> but if you compile under jdk 1.5, then it will NOT play under jre 1.3
<0> yes
<1> thats why im going to instal jdk 1.3
<0> that's why you should give them 1.5
<1> :)
<1> well ive already done that... i was thinking about rolling back next year though...
<0> you see that still doesn't make much sense to
<1> but i guess its sort of archaic
<1> i remember there were some annoying bugs in 1.3
<0> if you can control what they have at home give them all 1.5
<0> if you can control what they have at home 1.3 won't do much good either
<1> home i cant control
<0> as they may have 1.2 or 1.1 or no java
<1> i mean in school
<0> yes
<1> but yeah your right...
<0> so make sure they have the newest in school
<1> ok
<1> makes sense
<0> and tell them what they should install at home to run it
<1> so i guess microsoft really screwed java eh?
<1> by not including it
<0> well you cannot use microsoft's java (that is below 1.1 and not compatible)
<0> so best is to use sun (or alternatively IBM or some commercial 1.5 compliant jdk)
<0> besides your kids may work on linux or a mac at home
<0> which is no problem with java
<1> yeah i try to push linux all the time, but still the chances of them using linux are pretty slight
<1> and mac... shrug donno
<0> well java works on all 3, one of the nice things about it
<1> is mediatracker usable under swing?
<1> or is there a replacement?
<1> to load images...
<2> Gurus.. I am seeing inconsistent behavior between different platforms. What _exactly_ should a static block initializer run?
<2> When*
<3> it should run once when the cl*** is first loaded
<2> So for example, right after "foo.cl***.getCl***Loader()"
<2> ?
<3> if the cl*** is referenced, which it is, then yes
<3> foo is a cl***? It should be capitalised
<2> It does most of the time, but I have a machine where it does not. Cl***.forName() works every time.
<3> sounds odd
<2> Yeah.. sure does.
<2> On second glance, it looks like a 1.4 vs 1.5 problem.
<2> getCl***Loader() does not run the static block on jdk5
<3> hm how odd
<2> Ok.. more info. Looks like it depends on compilation.
<2> Targeting 1.4 works 1 way, and targeting 1.5 the other.
<2> http://java.sun.com/j2se/1.5.0/compatibility.html#incompatibilities
<2> #5
<2> Maybe that explains it.?
<4> indeed, that seems to explain it
Return to
#java
or
Go to some related
logs:
#mirc
#php
#AllNiteCafe
#chatzone
fedora sx8300 install
petitgirl
#skype
qahba
#AllNiteCafe
#MissKitten
|
|