On 5/10/07, Dan Webb <[EMAIL PROTECTED]> wrote: > > > Any good? >
It's awful :P No, seriously - how often do people copy instance methods around? Is the minority really enough to justify the mass binding on each instance creation? How about solving the problem in a real way, by realizing what you're doing an compensating for that: func = a.showA.bind(a) In my opinion, if you're doing something weird then go ahead, just be aware of the scope change and know how to handle it. Any problems Im not thinking of? Yeah. What if I want to copy the instance method somewhere else, but I want it to change scope? If it was bound that I can't bind it to anything else. So it's a potential blocker in some cases. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Prototype: Core" 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 http://groups.google.com/group/prototype-core?hl=en -~----------~----~----~----~------~----~------~--~---
