09.02.2012, 16:32
That's what I did last night. At one point I had ~5 queries using the caching method and all others weren't. I made all queries use caching (and looping through cached results is actually a lot faster than calling mysql_fetch_row in a loop), but the issue still persisted.
I saw xxmitsu having the issue a month ago. He solved it by not using floating point numbers, but from what I've seen around, that should not be an issue at all. Having "2" instead of "2.0" will just make the compiler generate a slightly bigger .amx with a call to a function which makes it into a floating point number (please do correct if I'm mistaken).
Currently I'm trying it out on Windows with this build. However since I can recall some differences between different VS builds, I'll be trying another version out soon and then will report back.
I saw xxmitsu having the issue a month ago. He solved it by not using floating point numbers, but from what I've seen around, that should not be an issue at all. Having "2" instead of "2.0" will just make the compiler generate a slightly bigger .amx with a call to a function which makes it into a floating point number (please do correct if I'm mistaken).
Currently I'm trying it out on Windows with this build. However since I can recall some differences between different VS builds, I'll be trying another version out soon and then will report back.