wx::thread(3pm) [debian man page]

Wx::Thread(3pm) 					User Contributed Perl Documentation					   Wx::Thread(3pm)

NAME

       Thread - using wxPerl with threads

SYNOPSIS

	 # the order of these use()s is important
	 use threads;
	 use threads::shared;
	 use Wx;

	 my $DONE_EVENT : shared = Wx::NewEventType;

	 my $worker = threads->create( &work );

	 # create frames, etc
	 my $frame = Wx::Frame->new( ... );
	 EVT_COMMAND( $frame, -1, $DONE_EVENT, &done );
	 $app->MainLoop;

	 sub done {
	     my( $frame, $event ) = @_;

	     print $event->GetData;
	 }

	 sub work {
	     # ... do stuff, create a shared $result value

	     my $threvent = new Wx::PlThreadEvent( -1, $DONE_EVENT, $result );
	     Wx::PostEvent( $frame, $threvent );
	 }

	 # event handler
	 sub OnCreateThread {
	     # @_ = () is necessary to avoid "Scalars leaked"
	     my( $self, $event ) = @_; @_ = ();

	     threads->create( ... );
	 }

DESCRIPTION

       Threaded GUI application are somewhat different from non-GUI threaded applications in that the main thread (which runs the GUI) must never
       block.  Also, in wxWidgets, no thread other than the main thread can manipulate GUI objects.  This leads to a hybrid model where worker
       threads must send events to the main thread in order to change the GUI state or signal their termination.

   Order of module loading
       It's necessary for "use Wx" to happen after <use threads::shared>.

   Sending events from worker threads
       "Wx::PlThreadEvent" can be used to communicate between worker and GUI threads.  The event can carry a shared value between threads.

	 my $DONE_EVENT : shared = Wx::NewEventType;

	 sub work {
	     # ... do some stuff
	     my $progress = new Wx::PlThreadEvent( -1, $DONE_EVENT, $progress );
	     Wx::PostEvent( $frame, $progress );

	     # ... do stuff, create a shared $result value
	     my $end = new Wx::PlThreadEvent( -1, $DONE_EVENT, $result );
	     Wx::PostEvent( $frame, $end );
	 }

       The target of the event can be any "Wx::EvtHandler"

   Receiving events from worker threads
       "Wx::PlThreadEvent" is a command event and can be handled as such.  The "->GetData" method can be used to retrieve the shared data
       contained inside the event.

	 my $DONE_EVENT : shared = Wx::NewEventType;

	 EVT_COMMAND( $frame, -1, $DONE_EVENT, &done );

	 sub done {
	     my( $frame, $event ) = @_;

	     print $event->GetData;
	 }

   Creating new threads
       Creating new threads from event handlers works without problems except from a little snag.  In order not to trigger a bug in the Perl
       interpreter, all event handler that directly or indirectly cause a thread creation must clean @_ before starting the thread.

       For example:

	 sub OnCreateThread {
	     my( $self, $event ) = @_; @_ = ();

	     threads->create( ... );
	 }

       failure to do that will cause "scalars leaked" warnings from the Perl interpreter.

perl v5.14.2							    2007-03-16							   Wx::Thread(3pm)

threads::shared(3pm)					 Perl Programmers Reference Guide				      threads::shared(3pm)

NAME

       threads::shared - Perl extension for sharing data structures between threads

SYNOPSIS

	 use threads;
	 use threads::shared;

	 my $var : shared;

	 my($scalar, @array, %hash);
	 share($scalar);
	 share(@array);
	 share(%hash);
	 my $bar = &share([]);
	 $hash{bar} = &share({});

	 { lock(%hash); ...  }

	 cond_wait($scalar);
	 cond_broadcast(@array);
	 cond_signal(%hash);

DESCRIPTION

       By default, variables are private to each thread, and each newly created thread gets a private copy of each existing variable.  This module
       allows you to share variables across different threads (and pseudoforks on Win32).  It is used together with the threads module.

EXPORT

       "share", "cond_wait", "cond_signal", "cond_broadcast"

       Note that if this module is imported when "threads" has not yet been loaded, then these functions all become no-ops. This makes it possible
       to write modules that will work in both threaded and non-threaded environments.

FUNCTIONS

       share VARIABLE
	   "share" takes a value and marks it as shared. You can share a scalar, array, hash, scalar ref, array ref or hash ref.  "share" will
	   return the shared rvalue but always as a reference.

	   "share" will traverse up references exactly one level.  "share($a)" is equivalent to "share($a)", while "share(\$a)" is not.

	   A variable can also be marked as shared at compile time by using the "shared" attribute: "my $var : shared".

	   If you want to share a newly created reference unfortunately you need to use "&share([])" and "&share({})" syntax due to problems with
	   Perl's prototyping.

       lock VARIABLE
	   "lock" places a lock on a variable until the lock goes out of scope.  If the variable is locked by another thread, the "lock" call will
	   block until it's available. "lock" is recursive, so multiple calls to "lock" are safe -- the variable will remain locked until the out-
	   ermost lock on the variable goes out of scope.

	   If a container object, such as a hash or array, is locked, all the elements of that container are not locked. For example, if a thread
	   does a "lock @a", any other thread doing a "lock($a[12])" won't block.

	   "lock" will traverse up references exactly one level.  "lock($a)" is equivalent to "lock($a)", while "lock(\$a)" is not.

	   Note that you cannot explicitly unlock a variable; you can only wait for the lock to go out of scope. If you need more fine-grained
	   control, see Thread::Semaphore.

       cond_wait VARIABLE
	   The "cond_wait" function takes a locked variable as a parameter, unlocks the variable, and blocks until another thread does a
	   "cond_signal" or "cond_broadcast" for that same locked variable.  The variable that "cond_wait" blocked on is relocked after the
	   "cond_wait" is satisfied.  If there are multiple threads "cond_wait"ing on the same variable, all but one will reblock waiting to reac-
	   quire the lock on the variable. (So if you're only using "cond_wait" for synchronisation, give up the lock as soon as possible). The
	   two actions of unlocking the variable and entering the blocked wait state are atomic, The two actions of exiting from the blocked wait
	   state and relocking the variable are not.

	   It is important to note that the variable can be notified even if no thread "cond_signal" or "cond_broadcast" on the variable.  It is
	   therefore important to check the value of the variable and go back to waiting if the requirement is not fulfilled.

       cond_signal VARIABLE
	   The "cond_signal" function takes a locked variable as a parameter and unblocks one thread that's "cond_wait"ing on that variable. If
	   more than one thread is blocked in a "cond_wait" on that variable, only one (and which one is indeterminate) will be unblocked.

	   If there are no threads blocked in a "cond_wait" on the variable, the signal is discarded. By always locking before signaling, you can
	   (with care), avoid signaling before another thread has entered cond_wait().

	   "cond_signal" will normally generate a warning if you attempt to use it on an unlocked variable. On the rare occasions where doing this
	   may be sensible, you can skip the warning with

	       { no warnings 'threads'; cond_signal($foo) }

       cond_broadcast VARIABLE
	   The "cond_broadcast" function works similarly to "cond_signal".  "cond_broadcast", though, will unblock all the threads that are
	   blocked in a "cond_wait" on the locked variable, rather than only one.

NOTES

       threads::shared is designed to disable itself silently if threads are not available. If you want access to threads, you must "use threads"
       before you "use threads::shared".  threads will emit a warning if you use it after threads::shared.

BUGS

       "bless" is not supported on shared references. In the current version, "bless" will only bless the thread local reference and the blessing
       will not propagate to the other threads. This is expected to be implemented in a future version of Perl.

       Does not support splice on arrays!

       Taking references to the elements of shared arrays and hashes does not autovivify the elements, and neither does slicing a shared
       array/hash over non-existent indices/keys autovivify the elements.

       share() allows you to "share $hashref-"{key}> without giving any error message.	But the "$hashref-"{key}> is not shared, causing the error
       "locking can only be used on shared values" to occur when you attempt to "lock $hasref-"{key}>.

AUTHOR

       Arthur Bergman <arthur at contiller.se>

       threads::shared is released under the same license as Perl

       Documentation borrowed from the old Thread.pm

SEE ALSO

       threads, perlthrtut, <http://www.perl.com/pub/a/2002/06/11/threads.html>

perl v5.8.0							    2002-06-01						      threads::shared(3pm)