No, the docs are already fixed for the next release: https://github.com/mootools/mootools-core/commit/7ea65fb75
On Sat, Dec 18, 2010 at 2:24 PM, אריה גלזר <[email protected]> wrote: > then the docs are wrong: > http://mootools.net/docs/core/Types/Function#Function:bind > > I'll file a bug then > > > On Sat, Dec 18, 2010 at 3:13 PM, Arian Stolwijk <[email protected]> wrote: > >> The mootools 1.3 version (without compatibility) should be compatible with >> ES5. >> >> >> On Sat, Dec 18, 2010 at 1:59 PM, אריה גלזר <[email protected]>wrote: >> >>> So, I know this has probably been discussed so I'm asking this out of >>> curiosity rather than filing a ticket- >>> I've noticed that ES5's bind method uses currying via a list of >>> comma-separated variables: >>> >>> function a(a,b,c){console.log(this.d + a+b+c);} >>> var b = a.bind({d:'a'},"b","c"); >>> b("d"); //abcd >>> >>> while mootools' bind method receives an array of variables for multiple >>> variable currying: >>> >>> //same function a >>> var b = a.bind({d:'a'},["b","c"]); >>> >>> Now, aside from the fact that I believe that the moo way is better and >>> better conforms with the rest of the moo API, it still doesn't conform with >>> ES5, and probably means that even browsers that do conform would still >>> require an emulation. >>> >>> Obviously this is an edge case 'cause currying is rarely used with bind, >>> but I'm still curios on the decision making (if there's already an online >>> discussion I'll be happy to read it instead). >>> Just the kind of things weekend readings bring up (specifically - >>> http://dmitrysoshnikov.com/notes/note-1-ecmascript-bound-functions/ >>> and from there I got to >>> >>> http://code.google.com/p/js-examples/source/browse/trunk/bind_emulation.js >>> ) >>> >>> -- >>> Arieh Glazer >>> אריה גלזר >>> 052-5348-561 >>> http://www.arieh.co.il >>> http://www.link-wd.co.il >>> >>> >> > > > -- > Arieh Glazer > אריה גלזר > 052-5348-561 > http://www.arieh.co.il > http://www.link-wd.co.il > >
