return in OOP

Code below is just to print a message. Nothing more. Question is: Whether we have the line return $this->myname; or not, it works fine but why some people still use return in such cases? Is it just a matter of taste or I'm missing something about OOP? Example below might look silly but I just wanted to explain what I meant.

I don't see the necessity of using return $this->myname;.. if this is going to be use by other methods below it.Otherwise, when it is needed to be somewhere else without the hello.

Most coders use the same style, but ONLY for the purpose of method chaining. However, the approach is completely different from your codes above, because it only return->$this and not the whole thing..

Here is a sample code for method chaining.. Zend uses this a lot... I also see this a lot on my older brothers source codes, up to the extent of chaining multiple classes..

Seing people using return $this->myname part was making me think that it was a kind of "COMMIT" statement like we have have in DB queries. If the line $this->myname = $name; sets and reflects the changes instantly then there is no point of using return $this->myname. Just an extra unnecessary line.