search for: goxapian

This is probably more useful to the general list. Thanks for the update, Dave — was this based on the previous golang bindings? J > Begin forwarded message: > > From: Dave Courtois <dave.courtois60 at gmail.com <mailto:dave.courtois60 at gmail.com>> > Subject: GoXapian > Date: 27 October 2018 at 15:27:09 BST > > Hi there just a little word to tell you that Xapian 1.4.6 work in Golang 1.9. There is some issue with the MSet ESet, the namespace part of the name is drop by swig. There is also some error with define macro in .i files, but with minor change a...

...macro in .i files, but with minor change all work perfectly. I made > use of it as a search engine (and db), for my Javascript framework > named CargoWebserver. Here is the link to the golang port, > https://github.com/CargoWebServer/CargoWebServer/tree/master/Project/src/code.myceliUs.com/GoXapian > <https://github.com/CargoWebServer/CargoWebServer/tree/master/Project/src/code.myceliUs.com/GoXapian>. Good stuff. > I can wrote some unit test as you want, do you have some already > written for Java or C++... There are a lot of unit tests for the C++ bindings (in xapian-core/...

Hi Olly, I setup the environment for the golang branch and build it without problem. Cgo complain about the generated cc file and dosent regonize it as swig generated file... curious. There no more problem with the MSet and ESet and all class seem to be generated in Go correctly. I will try tomorrow to manually invoke swig over your .i file and see if the code is generated properly. The file

On Mon, Nov 05, 2018 at 09:04:23PM +0000, Olly Betts wrote: > Dave Courtois wrote: > > Hi there just a little word to tell you that Xapian 1.4.6 work in > > Golang 1.9. There is some issue with the MSet ESet, the namespace part > > of the name is drop by swig. There is also some error with define > > macro in .i files, but with minor change all work perfectly. I had a