> Function#wrap somehow encapsulated that functionality for us, though
> it probably wouldn't be terribly handy for day-to-day usage.
Justin, it actually would : )
How many times have you output the string representation of any of
Element#methods(those which are directly on an element) just to see:
"function () { return __method.apply(null,
[this].concat($A(arguments))); }"
That's the job of #methodize, but you get the idea.
We were actually considering changing Function#wrap to accept optional
boolean parameter. It would indicate that "wrapped" function's
toString must be bound to an original function's toString. This is
often crucial for debugging.
- kangax
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Ruby
on Rails: Spinoffs" group.
To post to this group, send email to rubyonrails-spinoffs@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/rubyonrails-spinoffs?hl=en
-~----------~----~----~----~------~----~------~--~---
