But would that really be a problem? Function as an instance could have a different definition of bind that overrides the one from prototype.
I can see how this is maybe not most elegant approach, but would you ever need to bind a constructor to another object? Jürg On 1 May 2010, at 07:07, Brendan Eich wrote: > On Apr 30, 2010, at 10:28 PM, Garrett Smith wrote: > >>> It could be that we missed a chance to add Function.bind(callable, thisObj, >>> argsArray). Adding such a "static method" might have provided the desired >>> common utility usable without conflicts by libraries. We may yet add such a >>> Function.bind. >> >> Function.bind is already specified, isn't it? Function itself is a function. > > Oops, of course -- it would have to be called something else, or located > somewhere else. > > /be _______________________________________________ es-discuss mailing list [email protected] https://mail.mozilla.org/listinfo/es-discuss
