[Xapian-tickets] [Xapian] #555: API docs don't make the maximum value number clear
Xapian
nobody at xapian.org
Fri Dec 9 08:12:39 GMT 2011
#555: API docs don't make the maximum value number clear
---------------------------+------------------------------------------------
Reporter: james | Owner: olly
Type: defect | Status: closed
Priority: normal | Milestone: 1.2.8
Component: Documentation | Version:
Severity: minor | Resolution: fixed
Keywords: | Blockedby:
Platform: All | Blocking:
---------------------------+------------------------------------------------
Changes (by olly):
* status: new => closed
* resolution: => fixed
* severity: major => minor
* milestone: 1.3.0 => 1.2.8
Comment:
I've documented the range explicitly in the doc comment for the valueno
type for trunk in r16156 and for 1.2 in r16158.
I also changed the {{{static<valueno>(-1)}}} to {{{0xffffffff}}} for trunk
in r16157 - it seems to me this is better as it's more robust to changes
in the type width. If we really want to change the width globally, we can
do that when we break ABI (and remote protocol and serialisation
compatibility) since BAD_VALUENO means we are source compatible.
--
Ticket URL: <http://trac.xapian.org/ticket/555#comment:3>
Xapian <http://xapian.org/>
Xapian
More information about the Xapian-tickets
mailing list