Question 1

How do I handle asynchronous callbacks with nbind?

Accepted Answer

nbind callbacks are freed after the C++ function returns, so for async use, you must copy the nbind::cbFunction argument to a new instance and store it. The README warns about this and suggests workarounds for functions like setTimeout.

Question 2

nbind vs embind: which is better for Emscripten projects?

Accepted Answer

nbind is inspired by embind but offers a header-only approach and cross-platform support beyond Emscripten. If you're solely targeting asm.js, embind might be more integrated, but nbind provides flexibility for Node.js and Electron too.

Question 3

How to debug nbind modules in Node.js?

Accepted Answer

Use gdb with node, compile with -g flags by modifying nbind.gypi, and remove optimization flags. The debugging section in the README provides steps for both Node.js and browser environments, including invoking the browser debugger for asm.js.

Question 4

Can nbind work with C code without C++?

Accepted Answer

No, nbind requires C++11 for template introspection. For C code, you need to write a C++ wrapper that calls the C functions, as explained in the 'Binding plain C' section of the user guide.

Question 5

What's the performance impact of using nbind for large data?

Accepted Answer

nbind copies all data between C++ and JavaScript, which can be slow for large arrays or buffers. For performance-critical operations, consider using buffers directly or minimizing cross-language calls, as noted in the data structures section.

Question 6

How to generate TypeScript definitions with nbind?

Accepted Answer

After compiling your C++ code, run the included ndts tool with the path to binding.gyp. For example, 'npm run -s -- ndts . > lib-types.d.ts' generates definitions, as shown in the TypeScript usage guide.

nbind

What is nbind?

Overview

Use Cases

Best For

Related Projects

Found a gem we're missing?

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions