On Tue, Jun 19, 2012 at 9:51 PM, Henry Maddocks <[email protected]> wrote:

>
> I think the OP's question has shown the right approach. He understands the
> dangers so, in an effort to improve his skills, he has asked the question,
> how can he use this technique in a way that will cause the least amount of
> problems. We should be encouraging this.
>
>
And I answered the OP's question: he can cause the least amount of problems
by confining monkey-patching to his own apps, not in publicly distributed
gems. Or, if putting it in a gem, making it part of the publicly advertised
feature set of the gem, not a hidden surprise.

--
Avdi

-- You received this message because you are subscribed to the Google Groups 
ruby-talk-google group. To post to this group, send email to 
[email protected]. To unsubscribe from this group, send email 
to [email protected]. For more options, visit this 
group at https://groups.google.com/d/forum/ruby-talk-google?hl=en

Reply via email to