Optimal BNLS procedure?

[MyndFyre]

why would it be a long... it's a verBYTE. a byte value.

Because the Battle.net protocol sends it as a 32-bit value, not an 8-bit value.

This is most likely due to greater efficiency in reading and writing data that is aligned to the native word size of the processor.

[Barabajagal]

That's why you do CLng(Config.VerByte). You define the variable as a byte because it's more efficient to have a byte variable than a long variable. Then when you need to send it, you send it as a long.

[Ringo]

That's why you do CLng(Config.VerByte). You define the variable as a byte because it's more efficient to have a byte variable than a long variable. Then when you need to send it, you send it as a long.

Until a version byte exceeds 0xFF, and your program hits a problem

[Barabajagal]

oh noes, i'll have to set it to an int and release an update. how terrible. everyone else will also have to stop calling them verbytes then, too.

[Mystical]

I think you just like to argue with people, but wouldn't you mean CByte(Config.Verbyte) if you want it to be a byte? CLong() would be converting it to a long?


CLng Function:

Code Select Expand


CLng(expression)
Converts the value of expression to a Long data type. The argument expression must be a numeric value from -2,147,483,648 to 2,147,483,647. Fractions are rounded.


Cbyte Function:

Code Select Expand


CByte(expression)
Converts the value of expression to a Byte data type. The argument expression must be a numeric value between 0 and 255.


[Barabajagal]

that's the point... Config.VerByte is defined as a byte for less memory usage. the InsertDWORD requires a long, so you do CLng(Config.VerByte). and yes, I have a VERY argumentative nature.

[rabbit]

Or if you're using an even half-decent packet buffer you call your uint_32 insertion on the Config.VerByte and the procedure automatically converts it.