just did a napping session with that one. good to know i'm not alone.
good to know there's something being done by someone, too:
https://github.com/rvagg/nan
Native Abstractions for Node.js
*A header file filled with macro and utility goodness for making addon
development for Node.js easier a
thanks a lot!
--
--
Job Board: http://jobs.nodejs.org/
Posting guidelines:
https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
You received this message because you are subscribed to the Google
Groups "nodejs" group.
To post to this group, send email to nodejs@googlegroups.com
T
On Sat, Sep 21, 2013 at 7:22 PM, ~flow wrote:
> so the failure to compile is not inherent to an unstable node distro, it's
> just a (rather pervasive) accident of the API that a given module happens to
> use, right?
>
> this seems to imply that many unmaintained modules will not be available in
>
so the failure to compile is not inherent to an unstable node distro, it's
just a (rather pervasive) accident of the API that a given module happens
to use, right?
this seems to imply that many unmaintained modules will not be available in
0.12 unless fixes get published.
is there any guide h
On Saturday, September 21, 2013 12:22:50 PM UTC-4, ~flow wrote:
>
> is there a general reason this must be so? is there any trick / patch /
> configuration i can apply to remedy the situation? if a given module does
> compile on NodeJS 0.10.x, but fails on 0.11.x, should i expect it to
> compile
