Animation-CobThreads - Revision history

Flozi: 1cat

2013-03-21T10:55:30Z

1cat

← Older revision		Revision as of 11:55, 21 March 2013
Line 56:		Line 56:

	However, start-script ''does'' create a new thread, and the calling function ''doesn't'' wait until the started function returns before continuing. By default, the new thread shares the same signal mask as its parent, although you can set it manually if you like. Apart from this, the two threads execute completely independently.		However, start-script ''does'' create a new thread, and the calling function ''doesn't'' wait until the started function returns before continuing. By default, the new thread shares the same signal mask as its parent, although you can set it manually if you like. Apart from this, the two threads execute completely independently.
	~~[[Category:Unit_development]]~~
	[[Category:Animation]]		[[Category:Animation]]

Flozi: /* Source */ update to git using sourcelink template

2011-07-07T23:43:58Z

Source: update to git using sourcelink template

← Older revision		Revision as of 00:43, 8 July 2011
Line 1:		Line 1:
	==Source==		==Source==

	~~https://spring.clan-sy.com/svn/spring/trunk/~~rts/Sim/Units/~~COB~~/CobThread.cpp		{{sourcelink\|file=rts/Sim/Units/Scripts/CobThread.cpp}}

	==Introduction==		==Introduction==

Koshi: fix category

2010-03-13T17:38:25Z

fix category

← Older revision		Revision as of 18:38, 13 March 2010
Line 56:		Line 56:

	However, start-script ''does'' create a new thread, and the calling function ''doesn't'' wait until the started function returns before continuing. By default, the new thread shares the same signal mask as its parent, although you can set it manually if you like. Apart from this, the two threads execute completely independently.		However, start-script ''does'' create a new thread, and the calling function ''doesn't'' wait until the started function returns before continuing. By default, the new thread shares the same signal mask as its parent, although you can set it manually if you like. Apart from this, the two threads execute completely independently.
			[[Category:Unit_development]]
			[[Category:Animation]]

Seanheron: Animation:CobThreads moved to Animation-CobThreads: oops

2009-08-23T21:05:30Z

Animation:CobThreads moved to Animation-CobThreads: oops

← Older revision	Revision as of 22:05, 23 August 2009
(No difference)

Seanheron: COB Threads moved to Animation:CobThreads: convention

2009-08-23T20:58:01Z

COB Threads moved to Animation:CobThreads: convention

← Older revision	Revision as of 21:58, 23 August 2009
(No difference)

Evil4Zerggin at 23:04, 27 May 2008

2008-05-27T23:04:27Z

← Older revision		Revision as of 00:04, 28 May 2008
Line 13:		Line 13:
	Every time a callin is called or a start-script statement is executed, a "thread" is created. At any one time, only one thread is being executed at a time, but sometimes a thread will stop executing for a while and continue later, while several other threads will execute in the meantime. Most of the time your script is guaranteed to execute sequentially. If you say x = 1;, it will stay 1 unless you change it again. The exceptions are as follows:		Every time a callin is called or a start-script statement is executed, a "thread" is created. At any one time, only one thread is being executed at a time, but sometimes a thread will stop executing for a while and continue later, while several other threads will execute in the meantime. Most of the time your script is guaranteed to execute sequentially. If you say x = 1;, it will stay 1 unless you change it again. The exceptions are as follows:

	* Before a script starts.		*Before a script starts.
	* After a wait-for-move or wait-for-turn statement.		*After a wait-for-move or wait-for-turn statement.
	* After a sleep statement.		*After a sleep statement.

	During these times, any other thread has the ability to come in and change all your static variables, tell your pieces to move, turn, and spin, and so forth. Therefore, you cannot always assume these things will be the way you left them when execution of the thread resumes. If it is possible that another thread will change something that you need to know about, you need to check it after any of these times.		During these times, any other thread has the ability to come in and change all your static variables, tell your pieces to move, turn, and spin, and so forth. Therefore, you cannot always assume these things will be the way you left them when execution of the thread resumes. If it is possible that another thread will change something that you need to know about, you need to check it after any of these times.

Evil4Zerggin at 22:19, 27 May 2008

2008-05-27T22:19:33Z

← Older revision		Revision as of 23:19, 27 May 2008
Line 5:		Line 5:
	==Introduction==		==Introduction==

	Much of the time you can expect your script to execute sequentially; that is, looking through your code, the system progresses from statement to statement without anything "strange" (variables being changed, threads being started, etc.) between them. HOWEVER, "strange" things do happen, and in fact they happen quite regularly in scripts. We say that the script system has "concurrency".		Much of the time you can expect your script to execute sequentially; that is, looking through your code, the system progresses from statement to statement without anything "strange" (variables being changed, threads being started, etc.) between them. HOWEVER, "strange" things do happen, and in fact they happen quite regularly in scripts. We say that the script system has "concurrency" when things can happen between statements.

	===Why Concurrency?===		===Why Concurrency?===

Evil4Zerggin at 22:19, 27 May 2008

2008-05-27T22:19:02Z

@@ Line 24: / Line 24: @@
   sleep [time in ms];
 ==Signals==
 ==call-script==
 ==start-script==

Evil4Zerggin: New page: ==Source== https://spring.clan-sy.com/svn/spring/trunk/rts/Sim/Units/COB/CobThread.cpp ==Introduction== Much of the time you can expect your script to execute sequentially; that is, loo...

2008-05-27T22:05:09Z

New page: ==Source== https://spring.clan-sy.com/svn/spring/trunk/rts/Sim/Units/COB/CobThread.cpp ==Introduction== Much of the time you can expect your script to execute sequentially; that is, loo...

New page

==Source==

https://spring.clan-sy.com/svn/spring/trunk/rts/Sim/Units/COB/CobThread.cpp

==Introduction==

Much of the time you can expect your script to execute sequentially; that is, looking through your code, the system progresses from statement to statement without anything "strange" (variables being changed, threads being started, etc.) between them. HOWEVER, "strange" things do happen, and in fact they happen quite regularly in scripts. We say that the script system has "concurrency".

===Why Concurrency?===
So why go to all this trouble with concurrency? The script system has concurrency because we never know when things are going to happen. The player could give a command to the unit, the unit could run into a wall, rocks could fall out of the sky and kill the unit, and so forth. Without concurrency we would have to check very often whether which of all possible events had happened recently in order to determine what to do next. This would suck.

==Dealing With Concurrency==
Every time a callin is called or a start-script statement is executed, a "thread" is created. At any one time, only one thread is being executed at a time, but sometimes a thread will stop executing for a while and continue later, while several other threads will execute in the meantime. Most of the time your script is guaranteed to execute sequentially. If you say x = 1;, it will stay 1 unless you change it again. The exceptions are as follows:

* Before a script starts.
* After a wait-for-move or wait-for-turn statement.
* After a sleep statement.

During these times, any other thread has the ability to come in and change all your static variables, tell your pieces to move, turn, and spin, and so forth. Therefore, you cannot always assume these things will be the way you left them when execution of the thread resumes. If it is possible that another thread will change something that you need to know about, you need to check it after any of these times.

==Sleeping==

You can have a thread sleep by using a sleep statement:

sleep [time in ms];

==Signals==

==call-script==

==start-script==