Flag this message private class methods- functionality orshortcoming?

A

amit saxena

My apologies for resending but there were some formatting errors in the code.

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

class<<self
private
def fun
p "hello"
end
end

end

But if we write as:

class Abc

private
def self.fun
p "hello"
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
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Members online

No members online now.

Forum statistics

Threads
473,769
Messages
2,569,582
Members
45,069
Latest member
SimplyleanKetoReviews

Latest Threads

Top