Re[2]: (byte)((i 0x7f) | 0x80) == (byte)(i | 0x80)

2006-04-26 Thread Charlie
ok, thanks for your reply. But I thought Method: public void writeVInt(int i) is not about UTF-8, it is about how to write an int in variable length. Is it included as a part of future unicode character writing? -- Best regards, Charlie --- I thought (byte)((i 0x7f) | 0x80) ==

Re: Re[2]: (byte)((i 0x7f) | 0x80) == (byte)(i | 0x80)

2006-04-26 Thread Yonik Seeley
On 4/26/06, Charlie [EMAIL PROTECTED] wrote: ok, thanks for your reply. But I thought Method: public void writeVInt(int i) is not about UTF-8, it is about how to write an int in variable length. Oh, sorry... wrong function. It was a similar optimization to things I had seen in the char

Re: Re[2]: (byte)((i 0x7f) | 0x80) == (byte)(i | 0x80)

2006-04-26 Thread Marvin Humphrey
On Apr 26, 2006, at 10:21 AM, Charlie wrote: But I thought Method: public void writeVInt(int i) is not about UTF-8, it is about how to write an int in variable length. Is it included as a part of future unicode character writing? WriteVInt, and also WriteVLong, which contains the same

Re: Re[2]: (byte)((i 0x7f) | 0x80) == (byte)(i | 0x80)

2006-04-26 Thread Yonik Seeley
On 4/26/06, Marvin Humphrey [EMAIL PROTECTED] wrote: So the question is, does this assertion hold? (byte)((i 0x7f) | 0x80) == (byte)(i | 0x80) Yes. I tested just this out, and java5 -server reports a 15% performance boost for writeVInt alone, tested over numbers from 1 to 100. Of