[klippy]

In the end, it doesn't even matter.

[HamletEagle]

Stop over thinking, it doesn't matter.

[PurposeLessx]

So, I can use anything with get_players & for(new i=0......); ?

PHP Code:

new players[32]....
....
for(new i=0; i<inum; i++) {
        player = players[i];

       set_pev(player, pev_health, Float:pev(player_health) + 1.0);
} 


If so, I mean I am dealing nothing important things...

[Ghosted]

Well in my test first one was 2x faster than second and 2.5x faster than 3rd

[PurposeLessx]

Originally Posted by Ghosted Well in my test first one was 2x faster than second and 2.5x faster than 3rd

Did you test it with get_players and for(new.....)? or just in call per once?

[Ghosted]

Originally Posted by PurposeLessx Did you test it with get_players and for(new.....)? or just in call per once?

No just looped what u typed (about setting health) three of them (each one 32768000 times) 9 times and results were same all time. And also i used C++ .

EDIT:

Also tested in AMXX and in speed 1 > 2 > 3 but difference is not much

[OciXCrom]

Store values in variables only if they're used more than once. That's it.

[HamletEagle]

Originally Posted by OciXCrom Store values in variables only if they're used more than once. That's it.

I believe it's fine to use a variable even if the value is used one time, for readability.
Think about a pretty long native call inside another native call for example.

[klippy]

When it comes to performance it really comes down to reducing pawn-C++ interop, most of other stuff doesn't matter.

[PurposeLessx]

Originally Posted by HamletEagle I believe it's fine to use a variable even if the value is used one time, for readability. Think about a pretty long native call inside another native call for example.

May you give an example to use? I am not still pretty sure about what is it fine.
(My english is not good enough. I cannot understand, sorry my bad)