No subject

feeling many PHP (only) users out there would probably not understand why
their code is failing, and therefore waste a lot of time trying to figure
out what's going on, or just give up all together.

I think that there'd be a place for a better designed xapian wrapper to make
it accessible to the wider PHP community ('the masses'), so if i ever get a
chance i might take a look at what's possible, and see about doing away with
the existing xapian.php and come up with a different way to talk to the php
module.

PS. Sorry for the wordy reply :p

PSPS. While we're on the subject, 1.2.7 introduced issues with the
xapian.php wrapper with index_text() and index_text_without_positions()
returning $r values that dont exist (thus throwing php notices). I'll look
into logging it / fixing it / whatever, shortly.

PSPSPS. I think i even dismissed using xapian the first time i tried it a
couple of years ago, because i compiled on centos4 with the older patched
zlib 1.2.1 and it just segfaults, and at the time, there was no way i could
easily go and upgrade zlib on a dozen production servers.