Rajiv Rai wrote:Am confused about what the above statement means?
Basically, what it means is that you shouldn't rely on a method having a particular implementation when you call it. And I'd go further and say that the statement applies whether you're using interface inheritance or not.
When tutorials refer to 'behaviour', they usually mean methods; when they talk about 'implementation', they're referring to code. You can call a method without having to know the code it contains.
Bats fly at night, 'cause they aren't we. And if we tried, we'd hit a tree -- Ogden Nash (or should've been).
Articles by Winston can be found here