From: David Mark on
Garrett Smith wrote:
> Thomas Allen wrote:
>> On Apr 14, 6:29 pm, Thomas 'PointedEars' Lahn <PointedE...(a)web.de>
>> wrote:
> [...]
>
>> // Didn't want to use in operator and for in loop does not
>> preserve order
>> while (i--) {
>>
>
> That looks like reverse loop to populate an array followed by a call to
> reverse(). He certainly goes to a lot of trouble slow things down.

You certainly go to a lot of trouble to do nothing. :)
From: David Mark on
Thomas Allen wrote:
> On Apr 14, 6:29 pm, Thomas 'PointedEars' Lahn <PointedE...(a)web.de>
> wrote:
>> However, I would not feature-test Function.prototype.call() and then call
>> Function.prototype.apply(), and vice-versa. The rule of thumb for feature-
>> testing is: Always test exactly what you are using later. (Perhaps there
>> is also a canApply in My Library?)
>
> Certainly Function.prototype.apply can do anything that
> Function.prototype.call can, so the thrust of my inquiry is: Does the
> absence of the former really make the entire following code
> unnecessary or useless? Or did the author assume that any browser
> which lacks call would also lack apply?

Yes, if call is not there, forget apply. ;)