I'd lean toward keeping UInt32 in general, so at least that will scale to 4B documents. SegSize is the only place where UInt32 is used that it will matter (all of the other uses will never approach that size).
writeInt() writes both signed and unsigned integers (or rather the bit pattern could be interpreted as either, and it's up to the definition to decide which it is). You're right about FORMAT... something should be changed to make it consistent. It could be defined as 0xffffffff instead of -1. -Yonik On 9/22/05, Marvin Humphrey <[EMAIL PROTECTED]> wrote: > > Greets, > > The File Formats document indicates that Lucene's primitive datatypes > include a UInt32, but writeInt actually writes signed ints. In fact, > if that weren't the case, FORMAT couldn't be specified as a negative > number. Should UInt32 be Int32 instead? > > It looks like the same holds true for the UInt64 datatype. > > Marvin Humphrey > Rectangular Research > http://www.rectangular.com/ > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- -Yonik Now hiring -- http://tinyurl.com/7m67g
