From: amit saxena <amit83.saxena@...>
Date: 2008-06-09T23:01:09+09:00
Subject: private class methods- functionality or shortcoming?

--0-177072329-1213020073=:53740
Content-Type: text/plain; charset=us-ascii

I just switched to Ruby and came across it.
If we have to make a class method private then we should write it as:

class Abc
&nbsp;&nbsp;&nbsp; 
&nbsp;&nbsp;&nbsp; class&lt;&lt;self
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; private
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; def fun
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; p "hello"
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; end
&nbsp;&nbsp;&nbsp; end
&nbsp;&nbsp;&nbsp; 
end

But if we write as:

class Abc
&nbsp;&nbsp;&nbsp; 
&nbsp;&nbsp;&nbsp; private
&nbsp;&nbsp;&nbsp; def self.fun
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; p "hello"
&nbsp;&nbsp;&nbsp; end

end

then the class method is not private but behaves as public.

So, is it a carefully designed functionality? If so, then what is the thinking behind it?
OR any other reasons behind it?
Somebody told me that ruby encourages to define class methods the first way.
But I think that if you are giving more than one methods to do a thing, then all should function the same way.

Thanks and Regards,
Amit



      
--0-177072329-1213020073=:53740--