wood burning stoves 2.0*
The moose likes Beginning Java and the fly likes Dynamic method resolution Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login
JavaRanch » Java Forums » Java » Beginning Java
Bookmark "Dynamic method resolution" Watch "Dynamic method resolution" New topic
Author

Dynamic method resolution

Kannan BLR
Greenhorn

Joined: Mar 01, 2005
Posts: 10
Hi friends,

Advantage of interface is Dynamic method resolution. I saw that one in some books.But I don't know about Dynamic method resolution.
please Any one help me .


Kannan.A<br />kannanmsc@sify.com
Stan James
(instanceof Sidekick)
Ranch Hand

Joined: Jan 29, 2003
Posts: 8791
When you ihave a variable or argument whose type is an interface, the compiler can be sure the object that the variable refers to at runtime will have the method. But the compiler can't locate the exact code for that method because all it knows for sure is the interface.

Suppose you have a method that takes a List argument and you call a method on the argument. At runtime the JRE has to dynamically call the code defined in the object that's really passed in. It might be the LinkedList code or the ArrayList code. In the early days of OO this dynamic lookup was considered by some to be a fatal flaw - too much overhead and almost guaranteed to cause virtual memory paging. Nowadays it's taken for granted.

More clear or less?
[ May 14, 2005: Message edited by: Stan James ]

A good question is never answered. It is not a bolt to be tightened into place but a seed to be planted and to bear more seed toward the hope of greening the landscape of the idea. John Ciardi
vignesh gopalakrishnan
Greenhorn

Joined: Jun 27, 2012
Posts: 20
Stan James wrote:When you ihave a variable or argument whose type is an interface, the compiler can be sure the object that the variable refers to at runtime will have the method. But the compiler can't locate the exact code for that method because all it knows for sure is the interface.

Suppose you have a method that takes a List argument and you call a method on the argument. At runtime the JRE has to dynamically call the code defined in the object that's really passed in. It might be the LinkedList code or the ArrayList code. In the early days of OO this dynamic lookup was considered by some to be a fatal flaw - too much overhead and almost guaranteed to cause virtual memory paging. Nowadays it's taken for granted.

More clear or less?
[ May 14, 2005: Message edited by: Stan James ]



stan james .. i did read the information you provided for this thread . i can sense some information what you are trying to say . but i can't get enough crystal clear answer sir .. so , if you don't mind show me with a powerful example that which will never ever get out from my mind. please..??
Matthew Brown
Bartender

Joined: Apr 06, 2010
Posts: 4343
    
    8

He wrote that seven years ago, so I think there's a fair chance Stan isn't following this thread any more.
Henry Wong
author
Sheriff

Joined: Sep 28, 2004
Posts: 18520
    
  40

http://www.coderanch.com/t/3359/Ranch-Office/Stan-James-RIP


Books: Java Threads, 3rd Edition, Jini in a Nutshell, and Java Gems (contributor)
vignesh gopalakrishnan
Greenhorn

Joined: Jun 27, 2012
Posts: 20
Matthew Brown wrote:He wrote that seven years ago, so I think there's a fair chance Stan isn't following this thread any more.



oh. that's ok . thanks anyways matthew brown .
 
It is sorta covered in the JavaRanch Style Guide.
 
subject: Dynamic method resolution
 
Similar Threads
Method References
Screen resolution
Dyanmic Screen Resolution in J2ME
screen resolution problem
Regarding System.currentTimeMillis();