Re: Monkeypatching is Destroying Ruby
- From: Clifford Heath <no@xxxxxxxxxxxxxxx>
- Date: Wed, 27 Feb 2008 09:25:17 +1100
Pit Capitain wrote:
Could you describe "the general thing" a little bit more? As I
understood it, he wants to limit a "monkey patch" to the scope of a
Module. Which is what I've done. I've only used the import-module
library and added a more user-friendly syntax. I'm not inspecting
caller at all, and import-module doesn't either. What am I missing?
Well, I can't find import-module-extended, but assuming it's like
import-module... you're missing:
* performance
* isolation of instance variables that the extensions might create
* ability for an extended class to *always* appear extended when
called from anywhere in a class that knows about those extensions,
without having to constantly remember to add the extensions on each
call.
Is that enough to claim "no sensible way" of doing it?
.
- Follow-Ups:
- Re: Monkeypatching is Destroying Ruby
- From: Pit Capitain
- Re: Monkeypatching is Destroying Ruby
- References:
- Monkeypatching is Destroying Ruby
- From: Avdi Grimm
- Re: Monkeypatching is Destroying Ruby
- From: Phlip
- Re: Monkeypatching is Destroying Ruby
- From: Clifford Heath
- Re: Monkeypatching is Destroying Ruby
- From: Pit Capitain
- Re: Monkeypatching is Destroying Ruby
- From: Clifford Heath
- Re: Monkeypatching is Destroying Ruby
- From: Pit Capitain
- Monkeypatching is Destroying Ruby
- Prev by Date: Re: open-uri bug
- Next by Date: Re: Array help needed
- Previous by thread: Re: Monkeypatching is Destroying Ruby
- Next by thread: Re: Monkeypatching is Destroying Ruby
- Index(es):
Relevant Pages
|