search for: valuecountmatchspy

...t to create a patch, should it be against the xapian-bindings > directory/repo? or somewhere else? Against the search-xapian directory of the git repo would be best. Hey, I made a branch from svn/1.2 on github, and tried to forward port? the changes to this branch. I managed to wrap the ValueCountMatchSpy, and write tests to ensure it is working. In the original code there was also some code for PerlMatchSpy, but I did not manage to get this working yet. My XS/C-skills are rather limited unfortunately. If someone with more XS-exerpience could take a look and provide some feedback, that would be gr...

Can I use xapian for a search like: 'title' has the phrase "dinner jacket" AND 'color' == BLACK AND 'state' == MA AND 'size' == XL What about faceted search? Thanks

...quot;, line 6920, in _enquire_match_spy_add _enquire_add_matchspy_orig(self, decider) TypeError: in method 'Enquire_add_matchspy', argument 2 of type 'Xapian::MatchSpy *' Am I missing something obvious here, or is swig misbehaving? The above works if ms is an instance of xapian.ValueCountMatchSpy, but I need to implement something different to this. I'm running the latest Xapian from Debian sid: >>> xapian.version_string() '1.2.3' Thanks, Munchkin

...Looks plausible to me. I'd suggest that ~Enquire_perl() just call ref_clear_matchspies(NULL); rather than repeating all its code inline. > I created a pull request[1]. I would like to get the PerlMatchSpy thing > working as well, but it might be better to get the wrapping of the? > ValueCountMatchSpy merged/released regardless of the PerlMatchSpy > thing? The classes like perlMatchDecider are there to support passing a code reference in Perl where the C++ API wants a functor object. But Xapian::MatchSpy is rather more than just a function wrapped in a class, so I'm not sure it's ve...

Hey I?m cleaning up some code at my work place, and it turns out someone had forked Search::Xapian and added MatchSpy bindings for it for one of our internal projects. I was wondering if I should try to extract this as a patch against the current Search::Xapian code, and submit it, or if that is not wanted/wasted effort? It seems to be against 1.2.4.n of Search::Xapian, but I think I should be