[Bakr]

Quote:

Originally Posted by xVIP3Rx So you say that the end user is able to get the global "New"s in samp ? Or you mean for other programs ?

Lets say you create a library that runs on a specified timer. In the include you retrieve this timer and store it in a variable so you can delete it at server close - this variable is g_Timer. In your script that you include that library, they can access and modify the g_Timer variable, which in return can completely screw up the library. This is just one example, there are multiple other cases.

Here is a quick example:

pawn Code:

// timer.inc
// the include that runs off the timer

// declare the variable to store the timer ID so we can kill it later on
new g_Timer;

// Initialize the timer when the mode starts by hooking OnGameModeInit
hook OnGameModeInit() { g_Timer = SetTimer(...); }

// Kill the timer when the mode ends by hooking OnGameModeExit()
hook OnGameModeExit() { KillTimer(g_Timer); }

Now, here is the script that includes that library

pawn Code:

// test.pwn

#include <timer>

stock RandomFunction()
{
    // Here the "g_Timer" variable's value is altered meaning we no longer have the correct
    // timer ID to kill via our library
    g_Timer = SetTimer(...);
}

If you had declared the "g_Timer" variable as static, the test.pwn script wouldn't have been able to access the variable and screw things up. The static keyword is not only there to prevent things like this, but also hide implementation details from the end user. It's good programming practice. Like I've said, look up encapsulation.