From: Peter <Peter.Vanbroekhoven@...>
Date: 2004-12-06T18:30:26+09:00
Subject: Re: [ANN] patch to "make def return something useful"

> Yep, just that that was the only way I could get it to work right with my 
> still limited knowledge :-) Thanks for showing me how to remove them.

But maybe an extra clarification: in the end I settled for the solution 
with Method#private! instead of looking further for the bug that plagued 
my other approach. The reason was that in a way it made sense to have 
those methods as well because even though "private def a ; end" looks 
nicer, it is IMO less OO than Method#private! . The downside of these 
methods is that they are public, while Module#private is private, which 
makes it very easy to change the class without reopening it (and, as I 
realize now, bypass the check of $SAFE). Any thoughts on this? Other 
pros/cons?

Peter