[Plugin] MultiThread

[Fro1sha]

Description:

This is MultiThread plugin. And I don't know what to write here . Examples speak for themselves.
http://en.wikipedia.org/wiki/Multith...rchitecture%29

Attention:

PAWN is not designed to be multi-threaded and there are no guarantees AT ALL on your data the moment you introduce threads.

Wrong using this plugin can significantly corrupt your gamemode.

How to use:

#include <thread>

Log:

• 0.1.6

  
  - Added new native CreateThreadEx( const pubname[ ] );
  

• 0.1.5

  
  - First release.
  

Natives:

native CreateThread( const pubname[ ] );
native CreateThreadEx( const pubname[ ] );
native DestroyThread( threadid );
native SleepThread( milliseconds ); // Use in thread (public)
native LockThread( threadid ); // Synchronize will return the id lock
native UnLockThread( lockid );

Example:

With CreateThread

new tickid;

public OnGameModeInit()
{
    tickid = CreateThread( "MyFunction" );
}

public OnGameModeExit()
{
    DestroyThread( tickid );
}

public MyFunction( threadid )
{
    printf( "tick(%d)...", threadid  );
        
    SleepThread( 1000 );
}

With CreateThreadEx

new bool:active;
new tickid;

public OnGameModeInit()
{
    tickid = CreateThreadEx( "MyFunction" );
}

public OnGameModeExit()
{
    active = false;
}

public MyFunction( threadid )
{
    active = true;
    
    while ( active )
    {
        printf( "tick(%d)...", threadid  );
        
        SleepThread( 1000 );
    }
}

Download:

• 0.1.6

  
  Thread(.inc + .dll + .so)
  Thread Source
  

• 0.1.5

  
  Thread(.inc + .dll + .so)
  Thread Source
  Thread Example(server time and object sreamer in thread)
  

[linuxthefish]

I'm confused about what this dose, is it just a different way to call a function?

[Fro1sha]

Originally Posted by linuxthefish

I'm confused about what this dose, is it just a different way to call a function?

http://en.wikipedia.org/wiki/Multith...rchitecture%29

If you speak Russian, i can explain it to you =)))

[linuxthefish]

Originally Posted by Fro1sha

http://en.wikipedia.org/wiki/Multith...rchitecture%29

If you speak Russian, i can explain it to you =)))

I didn't think it was to do with actual threads! I'm definitely going to be using this.

[Ronaldo_raul™]

will get in handy for ....pro scripter.....not a beginner like me.....

[Rysoku]

Can't this corrupt your computer?

[Fro1sha]

Originally Posted by ronaldoraul

will get in handy for ....pro scripter.....not a beginner like me.....

No this is very simple.

Originally Posted by Rysoku

Can't this corrupt your computer?

What?

[langricr]

I was actually wondering why there didn't seem to be a threading plugin yet, based on the source, the parameter known as 'pubname' defines a function to be executed by the thread. Also, I'm guessing the function loops until the thread is destroyed? If so, you should change that so that threads can die naturally without being told to, it is much easier to implement a loop than to perform logic to assume when would be a good time to call DestroyThread. That way you could also implement a OnThreadDeath callback.

That way something like this would work.

new bool:active;
new tickid;

public OnGameModeInit()
{
	tickid = ThreadCreate( "MyFunction" );
}

public OnGameModeExit()
{
	active = false;
}

public MyFunction()
{
	active = true;
	
	while ( active )
	{
		printf( "tick..." );
		
		SleepThread( 1000 );
	}
}

public onThreadDeath( threadid )
{
	if ( threadid = tickid )
		printf( "The tick thread has died naturally." );
}

Other than that, nice work!

[Fro1sha]

Originally Posted by langricr

I was actually wondering why there didn't seem to be a threading plugin yet, based on the source, the parameter known as 'pubname' defines a function to be executed by the thread. Also, I'm guessing the function loops until the thread is destroyed? If so, you should change that so that threads can die naturally without being told to, it is much easier to implement a loop than to perform logic to assume when would be a good time to call DestroyThread. That way you could also implement a OnThreadDeath callback.

That way something like this would work.

new bool:active;
new tickid;

public OnGameModeInit()
{
	tickid = ThreadCreate( "MyFunction" );
}

public OnGameModeExit()
{
	active = false;
}

public MyFunction()
{
	active = true;
	
	while ( active )
	{
		printf( "tick..." );
		
		SleepThread( 1000 );
	}
}

public onThreadDeath( threadid )
{
	if ( threadid = tickid )
		printf( "The tick thread has died naturally." );
}

Other than that, nice work!

This is variant not good. Very hard for pawn scripters and DestroyThread and not actual onThreadDeath( threadid ).

[langricr]

Originally Posted by Fro1sha

This is variant not good. Very hard for pawn scripters and DestroyThread and not actual onThreadDeath( threadid ).

I suppose people could just call DestroyThread at the end of the function, but it seems dangerous outside of that, what happens if you try to destroy a thread while its halfway through the function?

I recommend having a look at this, while its Java, it does give some insight as to the dangers of stopping a thread.

Stopping a thread with Thread.stop causes it to unlock all of the monitors that it has locked (as a natural consequence of the unchecked ThreadDeath exception propagating up the stack). If any of the objects previously protected by these monitors were in an inconsistent state, the damaged objects become visible to other threads, potentially resulting in arbitrary behavior. Many uses of stop should be replaced by code that simply modifies some variable to indicate that the target thread should stop running.