08.07.2010, 12:43
If you come to look at it, PAWN is actually an OOP language.
Why?
You have various AMX files, all of which are linked to one virtual machine.
Each AMX file can call functions in other instances, thus each AMX file can be seen as an object.
Edit: I'll make a code example now!
PAWN Gamemode1:
PAWN Filterscript1:
Guess what happens when a player connects? Oh wait, it's called! Thus it's an OOP language.
Why?
You have various AMX files, all of which are linked to one virtual machine.
Each AMX file can call functions in other instances, thus each AMX file can be seen as an object.
Edit: I'll make a code example now!
PAWN Gamemode1:
pawn Код:
#include <a_samp>
#pragma semicolon 0
main()
{
}
forward onSomeSortOfCallback()
public onSomeSortOfCallback()
{
print("This callback was called.")
}
pawn Код:
#include <a_samp>
#pragma semicolon 0
public OnPlayerConnect(playerid)
{
CallRemoteFunction("onSomeSortOfCallback")
}