aspose file tools*
The moose likes OO, Patterns, UML and Refactoring and the fly likes OOPS in System.out.println Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login
JavaRanch » Java Forums » Engineering » OO, Patterns, UML and Refactoring
Bookmark "OOPS in System.out.println" Watch "OOPS in System.out.println" New topic
Author

OOPS in System.out.println

nikhil yekhe
Greenhorn

Joined: Jun 29, 2007
Posts: 8
Hello,

I was asked to prove OOP concept when we use syntax System.out.println(<display to consol>). How does it fits in OOP and explain how it follows OOP.

I was totally stumped on two things:
1. What do I have to show to prove whether given thing (code) follows OOP?
2. How to do it in above example?
[ March 13, 2008: Message edited by: nikhil yekhe ]

Nikhil Y
Ilja Preuss
author
Sheriff

Joined: Jul 11, 2001
Posts: 14112
To me, the most important property of OOP is using runtime polymorphism as a tool to manage code dependencies.

Does that give you an idea for 2.?


The soul is dyed the color of its thoughts. Think only on those things that are in line with your principles and can bear the light of day. The content of your character is your choice. Day by day, what you do is who you become. Your integrity is your destiny - it is the light that guides your way. - Heraclitus
nikhil yekhe
Greenhorn

Joined: Jun 29, 2007
Posts: 8
Originally posted by Ilja Preuss:
To me, the most important property of OOP is using runtime polymorphism as a tool to manage code dependencies.

Does that give you an idea for 2.?


Can you please elaborate on that. I understood that somehow the polymorphism is used in it. But I am not getting proper idea how to explain . Also if I am not wrong then to prove whether the code follows OOP or not we need to show that it fulfills all 4 fundamentals of OOP. Correct me if I am wrong and please elaborate.

Thanks,
Nikhil

ps: Sorry for delay
Ilja Preuss
author
Sheriff

Joined: Jul 11, 2001
Posts: 14112
I don't think that there is a generally agreed upon definition for "code following OOP".

Personally, I don't think it's a boolean property - code isn't either object oriented or not. There are all kinds of shades of object orientation.
 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: OOPS in System.out.println