Difference: WritingTasks (45 vs. 46)

Revision 462013-02-08 - JavierDiaz

Line: 1 to 1
 
META TOPICPARENT name="DpHipe"
<-- ANALYTICS CODE - DO NOT EDIT -->
<-- Google Analytics script BEGIN -->
<-- Google Analytics script END -->
Line: 199 to 199
 
  • HIPE 12
    • The default syntax will be the new one and you no longer need to add __list__=True. var1, var2 = myTask() will work as is (given that myTask has two outputs defined, of course).
Changed:
<
<
Note that tasks with multiple outputs will have more restrictions regarding changes in their outputs (order is fixed, adding or removing outputs may result in syntax errors ...). If you want to keep the flexibility to evolve your task it is recommended that you evaluate moving to a task with just one compound output. The best time to do it is now (HIPE 11 development), as users will have to modify their calls, anyway. Also note that it is impossible for the task framework to know how the task has been called wrt the left side of an assignment (the framework just 'sees" the right hand side, i.e. see INFO Task perform: [Full Call] log messages).
>
>
Note that tasks with multiple outputs will have more restrictions regarding changes in their outputs (order is fixed, adding or removing outputs may result in syntax errors ...). If you want to keep the flexibility to evolve your task it is recommended that you evaluate moving to a task with just one compound output. The best time to do it is now (HIPE 11 development), as users will have to modify their calls, anyway. Also note that it is impossible for the task framework to know how the task has been called wrt the left side of an assignment (the framework just 'sees' the right hand side, i.e. see INFO Task perform: [Full Call] log messages).
  This is why most parameters are cleaned (reset to their default values) after a task is executed in Jython:
 
This site is powered by the TWiki collaboration platform Powered by Perl