We've discussed deprecating bindAsEventListener about half a dozen
times already, and it just doesn't make sense, for the reasons
expressed above. So there's no point in discussing this further. I
suggest this be clarified in the documentation.

Regarding partial application in Function.prototype.bind, that's been
part of Prototype for a very long time and is part of the ES 3.1
specs, so that will stay in there too.

Robert, your solution using a single argument array per bound function
and resetting it's length on each bound method call is a huge
improvement over what we had before and has to go in imho.

I'd like to see how we can make the source code cleaner and use the
benefits of that technique for currying, etc.

The difficulty of abstracting your solution comes from the need for
the bound function to keep a reference to the original length of the
array so a to reset it before passing it to the original function.

I suspect that the cleanest solution might be to keep a generic array
updating method and reset the original before calling it.

Thoughts and implementation ideas welcomed.

Best,

Tobie


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Prototype & script.aculo.us" group.
To post to this group, send email to prototype-scriptaculous@googlegroups.com
To unsubscribe from this group, send email to 
prototype-scriptaculous+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/prototype-scriptaculous?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to