Hi Pito,
On 06/05/2012 12:09 PM, pito wrote: > Hi, I've read the .pdf document on the amforth's multitasker and, as > I am a newbie with it, I am overhelmed by a term "task" and its > snip... The whole concept is called ``cooperative multi_task_ing'' not multi_thread_ing. A task is much closer to a "process" than to a "thread". Threads share code space AND data space as well. In particular, variables are accessible from each thread simultaneously, therefore locking is needed. Threads are normally contained in a process, see e.g. [1] (Forth)-Tasks have separate data and return stacks. They share the code space (there is only one set of active wordlists). You do not neccessarily need locking of resources, because one task is running until it gives up control (by calling ``pause''). Does this help? Cheers, Erich [1] http://en.wikipedia.org/wiki/Cooperative_multitasking ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Amforth-devel mailing list for http://amforth.sf.net/ Amforth-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/amforth-devel
