search for: op_weight_cutoff

...ht cutoff); void set_elite_set_size(Xapian::termcount size); Xapian::termcount set_length(Xapian::termcount qlen); The private non-const methods are only used during construction, so they're not a problem. I tend to favour (b). The first three are tied to particular OPs (OP_NEAR/OP_PHRASE, OP_WEIGHT_CUTOFF, and OP_ELITE_SET respectively) so are perhaps cleaner that way anyway. The last is more awkward as a constructor parameter - it would perhaps be better replaced by an optional parameter to Enquire::set_query(). This is an API change (unlike (a)), but not one which is hard to update user code for...