According to ECMAScript 262, the context argument to every, forEach and ...

[dotnetCarpenter]

According to ECMAScript 262, the context argument to every, forEach and some should be undefined if not supplied. As an named argument, not supplied to a function is always undefined there should be no need to check that argument for a falsy value. Hence the function should run in an undefined context which in turn means it will run in the global context, which the caller code should be ignorant of as no context was supplied. <- CBuffer argumentation ;)
I have removed the extraneous code but found no tests to verify that CBuffer hasn't changed behavior other than my sane thinking think it should not.

[trevnorris]

Awesomeness. Good catch, and very well explained.

[dotnetCarpenter]

nice! I saw that the project had vows and installed it, but wasn't sure how
to use it. But still I haven't found any tests specific for forEach, some
and every. Must be me..

2012/11/23 Trevor Norris notifications@github.com

@dotnetCarpenter https://github.com/dotnetCarpenter Don't know if you
noticed, but if you do npm install you can then run the vows tests by
./node_modules/.bin/vows

—
Reply to this email directly or view it on GitHubhttps://github.com//pull/3#issuecomment-10654468.

[trevnorris]

@dotnetCarpenter To run the tests just run npm test, but you're correct in that I haven't created the unit tests for those methods. That's something I'm working on now.