On Feb 22, 2006, at 7:41 AM, Mathieu Bouchard wrote:
[...]
> Besides, i don't think that there's a point in having private/ 
> protected in
> Ruby. It's the feature I least care about. Especially because:
[...]

   I care about private methods actually being private.  One example;  
when writing gems with a binary extension component, I find myself  
writing classes half in Ruby and half in C with many of the C methods  
being private due to either having horrible calling conventions that  
shouldn't be exposed or worse, being something that could cause a  
crash if used incorrectly.

-tim