From: Ryan Davis <ryand-ruby@...>
Date: 2008-04-25T10:24:25+09:00
Subject: Re: Is there any nomenclature for private methods?


On Apr 24, 2008, at 16:49 , Iņaki Baz Castillo wrote:

> I prefer 2) but until the end of class it's not easy to know if a  
> method is
> public or private/protected. So i'm thinking about use a special  
> nomenclature
> for private methods, for example:
>
> 	def _private_1
>
>
> Is there any "standar" for this? I've seen lost of ethods called  
> "__xxxx__"
> or "_xxxxx" but not sure the reason of that name.

I don't ever use private or protected, but I do use that naming  
convention to convey the notion. Don't use double-underscore, that's  
basically considered reserved.


   def _think_twice_before_calling
     ...
   end