different versions of libxml produce slightly different errors
This was holding a reference to the document and not allowing it to be cleaned up. closes #97
build changes (node-waf) and api refactoring
integrates better with existing error handling and stack printing
- no need to have a different class just for callbacks (less code)
If you want to parse a file, use the node fs module and then parseString.
- constructor function can take an object listing the callbacks (no longer does it provide an argument or require a function) - connect events to the parser using 'on' and other event emitter methods - setCallbacks no longer exists
- wrap some of the c++ classes in js (documented and easier to follow) - no longer can attributes and namespaces objects be created
simpler unit testing
- removed scons requirement - removed link to repo (redundant) - update test section
It was stale and unupdated anyway, there is git commit history.
Use the proper headers in the right files. Massive single header include files are bad form!
avoid using persistent handles for error objects
There is a special place in hell for codebases that do not use this flag :)
- libxml has hooks for allocation/deallocation, no need to manually trigger - remove dead code
using var[variable] is not valid c++
Last argument is an int for options
- remove tools in favor of monkey patching js helper methods (simpler build) - makefile uses npm where appropriate