• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Tim Cooke
  • Ron McLeod
  • Jeanne Boyarsky
  • Paul Clapham
Sheriffs:
  • Liutauras Vilda
  • Henry Wong
  • Devaka Cooray
Saloon Keepers:
  • Tim Moores
  • Stephan van Hulst
  • Tim Holloway
  • Al Hobbs
  • Carey Brown
Bartenders:
  • Piet Souris
  • Mikalai Zaikin
  • Himai Minh

JDK1.3 and JDK1.1

 
Ranch Hand
Posts: 44
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
In principle, if I write a code using JDk1.1, it should always be compiled and run successfully using jdk1.3, right ?
Now, if it uses some depracate methods, will JDK1.3 just give warning but still compile/run well, or will JDK1.3 make the compilation completely fail ? Is there any web site resource giving a list of any deprecate method/class for jdk1.1 ?
Thanks,
Ian
 
Ranch Hand
Posts: 732
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
i think until now all the deprecated methods were not deleted.
so, i think you will have no problem running it under 1.3 .
you will only get a warning that u are using deprecated methods.
some of the bartenders may know of some deprecated mehtods that were deleted, but in my opinion , sun most of the time keeps backwards (or forward) compatibility.
 
Ranch Hand
Posts: 399
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
For the most part, java code is upward compatible from one release to the next. However, there can be incompatible changes. For example, I've not looked at 1.4, but I suspect the addition of the assert statement may break some earlier code. And in moving form JDK 1.2.2 to 1.3, there are some changes in Swing that can affect programs, although they may involve less frequently used features. As I recall, Sun avoids making changes that will break code when they change the third level, e.g, from 1.3.0 to 1.3.1, but will sometimes make such changes when they change the second level, e.g, 1.2.2 to 1.3.0. My working assumption is that code requires testing to be moved forward from 1.1 to 1.2, 1.2 to 1.3, and 1.3 to 1.4, but that the effort required fix problems will be small.
 
reply
    Bookmark Topic Watch Topic
  • New Topic