Changes between Version 18 and Version 19 of DsxDocumentation

Timestamp:

Feb 10, 2008, 7:46:49 PM (17 years ago)

Author:

Nicolas Pouillon

Comment:

--

DsxDocumentation

@@ -96 +96 @@
 As a software application can have several instances of the same task, we must distinguish the task, and the task model. A task model defines the code associated to the task, and the task interface corresponding to the system resources used by the task (MWMR communications channels, synchronization barriers, locks, memspaces, ...).
 {{{
-task_model = TaskModel( 'model_name',
+TaskModel( 'model_name',
                     ports = { 'inport' : MwmrInput(32) ,
                               'ouport'  : MwmrOutput(64) ,
@@ -167 +167 @@
 
 A task is an instance of a task model. The constructor arguments are the task name ''task_name'', the task model
-''Task_Model'' (created by the TaskModel() function), and a list of resources (MWMR channels, synchronization barriers, locks or memspaces), that must be associated to the task ports. DSX performs type checking between the port name and the associated resource.
+''model_name'', refered by name (created by the TaskModel() function), and a list of resources (MWMR channels, synchronization barriers, locks or memspaces), that must be associated to the task ports. DSX performs type checking between the port name and the associated resource.
 {{{
 my_task = Task( 'task_name',
-                         task_model ,
+                         'model_name' ,
                          portmap = { 'port_name' : my_channel, 'barrier_name' : my_barrier, ... } )
 }}}
@@ -185 +185 @@
 my_tcg = Tcg( 
              Task(  'task_name1, 
-                     Task_Model1, 
+                     'model_name1', 
                      portmap = { ’in’:input, ’out’:output } ), 
              Task(  'task2', 
-                     Task_Model2, 
+                     'model_name2', 
                      portmap = { ’in’:input2, ’out’:output2 } ) 
               ... )