<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>oop on Jaaved Ali Khan</title><link>https://jaaved.netlify.app/tags/oop/</link><description>Recent content in oop on Jaaved Ali Khan</description><generator>Hugo -- gohugo.io</generator><language>en-us</language><lastBuildDate>Sat, 14 Jan 2023 20:23:30 +0400</lastBuildDate><atom:link href="https://jaaved.netlify.app/tags/oop/index.xml" rel="self" type="application/rss+xml"/><item><title>Difference between messages and methods</title><link>https://jaaved.netlify.app/notes/20210808211117-difference_between_messages_and_methods/</link><pubDate>Sat, 14 Jan 2023 20:23:30 +0400</pubDate><guid>https://jaaved.netlify.app/notes/20210808211117-difference_between_messages_and_methods/</guid><description>Summary fc # A method is tied to a particular object. You find this in languages like Java and C++ where the method is bound early to the object at compile time.
A message is an abstraction whereby the actual method that’s being called depends on runtime conditions. The object’s method is late-bound, thereby offering greater flexibility to the executing program.
In Smalltalk, for example, an object may receive a message to invoke a non-existent method.</description></item></channel></rss>