trevnorris/cbuffer — pull request #3 by dotnetCarpenter (2012-11-22 06:04:16+00:00)
Title: According to ECMAScript 262, the context argument to every, forEach and ...

According to [ECMAScript 262](http://www.ecma-international.org/ecma-262/5.1/#sec-15.4.4.18), 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.