Node.js Foreign Function Interface For Windows
winffi is compiled product of node-ffi for windows and it's usage is the same
with node-ffi. node-ffi is a Node.js addon for loading and calling dynamic
libraries without writing any C++ code.
It also simplifies the augmentation of node.js with C code as it takes care of
of boilerplate code to your otherwise simple C. See the
for an example of this use case.
NOTICE: the different between winffi and node-ffi is the winffi doesn't dependent on any build tools that node-ffi need.
WARNING: node-ffi assumes you know what you're doing. You can pretty easily create situations where you will segfault the interpreter and unless you've got C debugger skills, you probably won't know what's going on.
var winffi = ;var libm = winffi;libm; // 2// You can also access just functions in the current process by passing a nullvar current = winffi;current; // 1234
For a more detailed introduction, see the node-ffi tutorial page.
- Only Support Windows.
- The current version is tested to run on node v0.6, v0.8, v0.9 and v0.10.
$ npm install @fxtop/winffi
The types that you specify in function declarations correspond to ref's types system. So see its docs for a reference if you are unfamiliar.
V8 and 64-bit Types
Internally, V8 stores integers that will fit into a 32-bit space in a 32-bit integer, and those that fall outside of this get put into double-precision floating point (FP) numbers. This is problematic because FP numbers are imprecise. To get around this, the methods in node-ffi that deal with 64-bit integers return strings and can accept strings as parameters.
There is non-trivial overhead associated with FFI calls. Comparing a hard-coded
binding version of
strtoul() to an FFI version of
strtoul() shows that the
native hard-coded binding is orders of magnitude faster. So don't just use the
C version of a function just because it's faster. There's a significant cost in
FFI calls, so make them worth it.
MIT License. See the