search

rimmartin / saxon-node

MIT License
64 stars 6 forks source link

Console output #13

Closed seanmcilvenna closed 5 years ago

seanmcilvenna commented 8 years ago

The SaxonProcessor.cpp file has a cout>> that gets output every time the module is used. I'd like to request that this be removed and some options be added to specify where logging information be sent like this (preferrably not always the console)

rimmartin commented 8 years ago

Yea, by Monday I'll have it clean; and building on mac windows and linux

rimmartin commented 8 years ago

I have it for nodejs v4.2.x Am testing 5.0.0.

For v0.12.x there i a tagged branch for which it can be done

seanmcilvenna commented 8 years ago

Oh great! This answers my question in https://github.com/rimmartin/saxon-node/issues/14 too :)

rimmartin commented 8 years ago

You in the situations your users are all nodejs versions? Back to v0.12.x or further?

I found a CentOS 5 reason to test the Excelsior JET tool for pure c++ application this week so should learn more about stability and error handling

seanmcilvenna commented 8 years ago

Sorry, missed this question. 0.12.x is as far back as we are targeting.

rimmartin commented 8 years ago

Hi @seanmcilvenna , will you need the Saxon/C 1.0.0 new api and new features back in v0.12.x branch?

seanmcilvenna commented 8 years ago

Hi @rimmartin , yes that would be ideal. Unfortunately, due to some other dependent modules, we aren't able to upgrade to the latest version of node.js yet... So, we are stuck with 0.12.7 until our dependent modules are fully compatible with v4.x.