Benjamin Byholm

Strange, I don't see any errors, apart from `NODE_MODULE(myaddon, Init);` having a semicolon, it should not have that -- but I don't think this is impacting the runtime behavior.

Sounds nice. I'll help out, starting with some thoughts I had straight away: Exercise 2 should also include cpplint (or some other linter, but I don't know of any). Apart...

You have a bunch of text and want to count how many times each word occurs (a histogram). Easiest way is to split the input domain (say there are 100...

parseInt or such? On June 29, 2014 9:32:52 PM EEST, Rod Vagg [email protected] wrote: > @trevnorris, @kkoopa (and others?) > > I've split up the 3rd exercise into two so...

Something else to point out: Scope, lifetime, garbage collection, memory management, persistent, weak and other handles.

That's an exposed method, so you should not use an escapable scope. On June 30, 2014 11:14:58 PM EEST, Rod Vagg [email protected] wrote: > all: I don't know how I'm...

Do not see how any of the changes could be related. The stack traces do not indicate any error with makecallback and the deprecation should not have affected anything, since...

I cannot exclude a bug in NAN, but I do not see how the changes since 2.9.2 could have this effect. [diff](https://github.com/nodejs/nan/compare/v2.9.2...v2.10.0#diff-558c37be49a47656e3ff41806c24bd33)

~~Then again, I now have a theory. `Nan::MakeCallback` now returns an empty handle upon failure. Perhaps it used to return `undefined` or such previously.~~ Nevermind.

Alright, found the cause of the error, you are doing an asynchronous call where you meant to do a synchronous call. This issue became prominent due to the new async...