On Tue, Jan 8, 2013 at 3:22 PM, Benjamin Farrell <[email protected]> wrote: > Awesome, I appreciate it! Onto the OpenNI forums! If anybody knows > otherwise I'd love to hear it so I'm not banging my head against the wall > needlessly. And honestly this is great news - I'm glad it wasn't what I was > afraid of - that this wasn't going to be possible in Node for some silly > reason.
There's one thing to keep in mind if the exceptions you mentioned are C++ exceptions: node.js itself doesn't use them - and is in fact compiled with -fno-rtti -fno-exceptions - so you need to catch any and all exceptions that library code throws. If you let one through, node.js (or rather, the C++ runtime) will abort. I didn't think of it yesterday, but if OpenNI throws an exception at dlopen() time (e.g. from a static constructor), it's game over. That would be a moronic thing to do, though. For one, you'd almost certainly leave the dynamic linker in an undefined state. -- 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 [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en
