On Sep 20, 2011, at 2:17 PM, Michael G Schwern wrote:

> #1 is fine so long as you have a reasonable expectation that your methods
> won't collide with somebody else.  If you're doing this in local code (ie. not
> a distributed library) that's fine.  I'd add a test to make sure DateTime
> itself does not add methods in the future.  The upside of this is you load
> your additional methods once and every object has it with no performance loss.
> This technique is often derided because it's widely abused in Ruby.

  http://justatheory.com/computers/programming/methodology/fuck-typing.html

Best,

David

Reply via email to