user/dev discussion of public-inbox itself
 help / color / mirror / code / Atom feed
From: Eric Wong <e@80x24.org>
To: meta@public-inbox.org
Subject: [WIP] searchidx: use "++" overloading in Search::Xapian::PostingIterator
Date: Sun, 16 Jun 2019 01:50:59 +0000	[thread overview]
Message-ID: <20190616015059.6036-1-e@80x24.org> (raw)

This makes it easier to be compatible with the SWIG-generated
"Xapian" bindings, which are currently lacking the "->inc" sub
implemented in the XS binding.

No plans to apply this to master, just yet.

My goal is to be compatible with both Search::Xapian XS
and the "Xapian" SWIG binding as long as possible; but the
SWIG binding is still not ready for prime-time, yet.

cf. https://trac.xapian.org/ticket/523
---
 lib/PublicInbox/SearchIdx.pm | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/lib/PublicInbox/SearchIdx.pm b/lib/PublicInbox/SearchIdx.pm
index 665f673..eb59d0d 100644
--- a/lib/PublicInbox/SearchIdx.pm
+++ b/lib/PublicInbox/SearchIdx.pm
@@ -382,7 +382,7 @@ sub batch_do {
 		my ($head, $tail) = $self->find_doc_ids($termval);
 		return if $head == $tail;
 		my @ids;
-		for (; $head != $tail && @ids < $batch_size; $head->inc) {
+		for (; $head != $tail && @ids < $batch_size; $head++) {
 			push @ids, $head->get_docid;
 		}
 		$cb->(\@ids);
@@ -437,7 +437,7 @@ sub remove_by_oid {
 	# there is only ONE element in @delete unless we
 	# have bugs in our v2writable deduplication check
 	my @delete;
-	for (; $head != $tail; $head->inc) {
+	for (; $head != $tail; $head++) {
 		my $docid = $head->get_docid;
 		my $doc = $db->get_document($docid);
 		my $smsg = PublicInbox::SearchMsg->wrap($mid);
-- 
EW


                 reply	other threads:[~2019-06-16  1:51 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://public-inbox.org/README

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20190616015059.6036-1-e@80x24.org \
    --to=e@80x24.org \
    --cc=meta@public-inbox.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/public-inbox.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).