Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Size Variables
#8
Dear william i will answer all you questions... plus more

Quote:Change it to Byte instead

Seeing as byte only goes up to 255 that would mean you could have only up to 255 players... hence integer which goes up to around 32000


Quote:It has proven that no speed change occur.

In a very large procedure like "handledata" it does make a difference and you can also save alot of space (text wise) because you can remove "if" "lcase parse" "then" and "exit sub"

Quote:Nothing in MS requires anything to be above 32000. So not sure if that is a good idea




thats my point change all longs to integer lol

Quote:Hum?

Bitfield in mirage was devised by someone i think it was dave not sure, which fits 8 booleans in a byte.

Quote:Isn't the difference between byte and long 2bytes or something?

No in vb6, byte = 1 long = 8

Quote:If you don't make a string fixed length, it uses 20 bytes + the string length MORE memory. Keep all the strings that you can fixed length.
Actually fixed length strings cause problems

Yes you would be right if everyone were to fill in all the spaces but...

Fixed-length strings are generally slower than conventional strings, because all VB string functions and operators only recognize conventional strings, thus all fixed-length strings must be transparently converted to and from conventional strings.
Reply


Messages In This Thread

Forum Jump:


Users browsing this thread: 1 Guest(s)