Cool. I got somewhere with prototyping using what I am calling couchbase-lite-node without a better term (couchbase-lite-core APIs mapped in node, using fastcall (an ffi package alternate to node-ffi) as a basis. Quickly became obvious though that although that works, debugging anything with the bindings is painful using it (sigsegv as only error info gets old real fast) and it’s nice to also get compile time information of any further couchbase-lite-core C API changes too. So I’m starting over with n-api.
Matias - - - - - Matias Piipari, PhD http://twitter.com/mz2 Manuscripts - A writing tool like nothing you have seen before http://manuscriptsapp.com On 24 Oct 2017, 17:52 +0100, Jens Alfke <[email protected]>, wrote: > > > > On Oct 22, 2017, at 5:20 PM, Matias Piipari <[email protected]> > > wrote: > > > > This sounds good. Do you follow some pattern for noting commits or release > > note entries where C API changes are introduced? > > I try to call this out in the commit message. So far it’s been informal > because it’s just three co-workers using this API to implement CBL, but if > there’s more development going on, we may want to establish clearer rules. > > Also, you can do a git diff of C/include/ to focus on changes to the API > headers. > > —Jens -- You received this message because you are subscribed to the Google Groups "Couchbase Mobile" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/mobile-couchbase/7e9952fb-a376-4b89-8950-4922b5d0651e%40Spark. For more options, visit https://groups.google.com/d/optout.
