• 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
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

Question related to jdk1.5

 
Ranch Hand
Posts: 328
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hello Everybody,
I want to ask two very simple questions:
1) Related to jdk1.5
Those who don't know about this:
I can write a code like this
import static System.out;
_________________
________________ //code continues
println("Hello World");// no need to write System.out
________________
_______________//code continues
Does anybody think that Static import in Jdk1.5 are really
useful?
Since i suppose they will create a dirty code which are not easy to maintain.
2) There is very basic question
Can we discuss about the issue as "Wheather Java is 100% Object Oriented Language?"
As far as i am concerned i think it is. But some people do have an arguments which are as follows:
i) Still we are using primitive data types.
ii) In OO language every object has definite state but in J2EE we do have Stateless Session Bean.
iii) One can define Objects without using 'new'operator.e.g. String

with best regards
Thanx in Advance
Shrinivas
 
author
Posts: 799
5
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
1. Use of static import is preferable to the Constant Interface (anti-)pattern that Joshua Bloch rails about in Effective Java. Certainly it can be abused, but I've found plenty of cases where its judicious use is effective.
2. I find little value in debating the OO-ness of Java. It is, never has been, and probably never will be 100% OO, but that doesn't mean it's not a good tool.

-j-
 
please buy my thing and then I'll have more money:
a bit of art, as a gift, that will fit in a stocking
https://gardener-gift.com
reply
    Bookmark Topic Watch Topic
  • New Topic