search for: boulton

Xapian has turned 20! Strictly speaking it was 20 years ago last month but I managed to miss the true anniversary - the oldest commit in the Xapian repo is: commit 8ced76ea128c8fb2792477e09b41fa989f2e572f Author: Richard Boulton <richard at tartarus.org> Date: Fri Sep 10 09:50:40 1999 +0000 Martins initial code, which didn't work for him but did for me. Back then Richard, Martin and I all worked for BrightStation, and Richard and I were working in a small office high above the foyer of St John's Innov...

Olly and I have been discussing details of our policy for deprecating features, and we thought it would be useful to canvas users opinions on a particular aspect. From time to time, we remove features from the library (usually because we have a better replacement). To make life easier for users, we've been following a deprecation policy, so that users are given plenty of warning of

Hi all, I'm trying to continue an existing m68k backend for LLVM. I'm completely new to LLVM development so I've been muddling my way through mostly by trial and error and using existing back ends for reference. I'm trying to implement code to allow calling. I am compiling this C code -- typedef unsigned int uint32_t; typedef char int8_t; uint32_t foo(uint32_t x, int8_t y) {

Hi, I'm confused about my licensing obligation with respect to the Xapian SWIG bindings. I've got a python wrapper that sits above the standard Xapian Python/SWIG bindings, and I wasn't sure if the *intent* of the Xapian team is that my python wrapper - and any code that also uses my wrapper also falls under GPLv2. It seems unclear if the FSF's position on dynamic linking in

...)); set_docid_order(Xapian::Enquire::ASCENDING); Why? What's the most efficient process to build multiple Xapian indexes? Can > the "relevance" index provide any hints to building the sorted indexes? > > Cheers, > Tim. > > On Tue, 2011-08-09 at 18:04 +0100, Richard Boulton wrote: > > On 9 August 2011 17:48, makao009 <makao009 at 126.com> wrote: > > > what is the fastest way to fetch results which are sorted by timestamp > ? > > > > The fastest possible way is to have your index sorted by timestamp > > (ie, such that document...

...ld largely solve the problem. Of course there are a wealth of addressing modes for the 68k, but they should be able to be dealt with like this I think? -----Original Message----- From: Dr D. Chisnall [mailto:dc552 at hermes.cam.ac.uk] On Behalf Of David Chisnall Sent: 09 July 2015 10:58 To: James Boulton Cc: llvmdev at cs.uiuc.edu Subject: Re: [LLVMdev] New backend help request. The simple answer is: not very easily. I’d be inclined to treat instructions like these as optimisations and ignore them (aside from integrated assembler support) until the rest of the back end is working. Once that’s w...

On Tue, May 11, 2004 at 05:41:58PM +0100, Richard Boulton wrote: > * If the queryserver can't parse a query, strip out all special > characters, and then retry. This means that we get some kind of > result even if the query is broken. That's probably a feature worth pushing down into Xapian::QueryParser... Cheers, Olly

On Thu, May 20, 2004 at 02:55:13PM +0100, Richard Boulton wrote: > Add debian packaging files to distribution tarball. > > Modified files: > xapian-core : Makefile.am You also need to add debian/Makefile.in to configure.in (I usually forget too). Probably debian/control.in too. Cheers, Olly

Yesterday I updated the deprecation.rst document such that I think it contains all the items which are slated for deprecation (and also contains full details of the upgrade suggestions, as Olly suggested). I've marked several things which have been deprecated for a long period of time (ie, since 0.9.0 or earlier) for removal in 1.0.0, in line with the policy outlined in the document. If

...tion, the copies of xapian_wrap.cc in the olde and modern subdirectories of the python binding sources are identical. I suspect that something has gone wrong with the source code generation... For now, I'm disabling python2.1 from the debian packages so that I can get them built. -- Richard Boulton <richard at tartarus.org>

I'm new to Xapian and we just recently upgraded to version 1.0.0.0. However, something seems to have changed during the upgrade and I need help figuring out how my code should be written. In version 0.9.9.1 of Search::Xapian, the following code results in this output "Xapian::Query(pet:(pos=1))". my $qp = new Search::Xapian::QueryParser; $qp->set_stemmer(new

I've now got working (but not necessarily policy compliant) debian packages for xapian-core, the xapian python bindings, and omega and omindex. I will be sorting out a public apt repository of these shortly. Is it appropriate to add the debian control files (ie, those files in the debian directories in CVS) to the distribution tarballs? I think yes - they don't take up much space,

Does anyone know if xapian stemming support suffix -er? I tried -s and -ing both work, but not -er. _________________________________________________________________ ?????????????? MSN Messenger: http://messenger.msn.com/cn

I'm trying to figure out how to map more complex CISC instructions now. For example on the 68000, you have things like -- add.w (a0)+,(a1)+ So that equates to: temp1 = load a0 add 2, a0 temp2 = load a1 temp1 = add temp1, temp2 store temp1, a1 add 2, a1 How do I express that in a form for LLVM? I see things like pre_store and post_store, but I cant find anything in the way of documentation

Hmm, I'm getting nowhere pretty fast. It seems 68000 with its CISC nature is quite complex to implement for a novice. I can see how to implement simple stuff, like -- move dn, dn move dn, (an) As that just turns into stores, sets, etc. But how would you represent things like indexed access? move dn, (an,dn) move dn, offset(an) Can I only really define very simple operations for the main

Hi, Is it possible to perform a search without flushing the index? I've got an application that updates the index every 4 hours but I need to be able to search the new data fairly quickly after the index is updated. The problem revolves around the fact that the update is often much less than 10 000 documents so it isn't being flushed until quite a bit latter. I realise I can do a flush

what is the fastest way to fetch results which are sorted by timestamp ? i want to use xapian as my search engine , use add_boolean_term(something) and add_value(0,sortable_serialise(get_timestamp())) to a doc. search through enquire.set_weighting_scheme(xapian.BoolWeight()) and enquire.set_sort_by_value(0,True) to ensure that the results are sorted by the timestamp. This method is ok , but

...lications currently using omindex. Finally, is there a problem with making any of these changes whilst we're within the 0.8.x version cycle, or is the expectation that the workings of omega and related tools will be reasonably stable within this cycle, as the API of libxapian is. -- Richard Boulton <richard@tartarus.org>

...re in 1.2.22. As always, if you encounter problems, please report them here, or to the bug-tracker: http://xapian.org/bugs The source tarballs are available from here: http://oligarchy.co.uk/xapian/1.3.4/ A big thankyou to the following people for helping to make this release a reality: Richard Boulton, coventry, Philip Neustrom, James Aylett, Will Greenberg, Emmanuel Engelhart, Dylan Griffith, Jorge C. Leit?o, UsusDei, boomboo, Charles Atkinson, Brian Burton, Gaurav Arora, Marco Hennigs, Thomas Viehmann, Pavel Strashkin, Mikkel Kamstrup Erlandsen, Brandon Schaefer, Dagobert Michelsen, matf, Germ...

One of the items on the ToDo list for version 1.0 at http://wiki.xapian.org/TodoFor1_2e0#preview is: "Rework Omega's indextext.cc as a xapian-core "TextSplitter" class." I've been wondering about this for a while now. Currently, we have the Query Parser in Xapian core, but no text processing. Clearly, it makes sense to have a "text splitter" class in