~scymtym/etasks/trunk

« back to all changes in this revision

Viewing changes to TODO

  • Committer: Jan Moringen
  • Date: 2010-07-19 02:03:14 UTC
  • Revision ID: scymtym@gmx.net-20100719020314-m0i51c0un1dpg9md
Handle errors during task execution by storing in execution.el
* execution.el (execution-result::error): new slot; stores error data
  that is generated during execution
  (execution-result::has-result-p): new method; check for result
  (execution-result::has-error-p): new method; check for error data
  (execution-result::future-done-p): use `has-result-p' and
  `has-error-p'
  (execution-blocking-result::initialize-instance): store signaled
  errors into error slot of result object
  (execution-result-idle::initialize-instance): likewise
  (execution-result-timeout::initialize-instance): likewise
  (execution-result-thread::initialize-instance): likewise
* TODO (how to handle signals): marked as DONE

Show diffs side-by-side

added added

removed removed

Lines of Context:
6
6
    + signal
7
7
* TODO Compute result lazily in blocking-execution?
8
8
* TODO Should it be possible to execute tasks more than once?
9
 
 
10
 
* TODO How to handle signals from task code?
11
9
* TODO How to collect and display errors during execution?
12
10
* TODO Hierarchy of tasks?
13
11
  Example
15
13
    + Prepare
16
14
    + Copy
17
15
 
 
16
* DONE How to handle signals from task code?
 
17
  We store the signaled data into an :error slot of the result object
 
18
  and consider the execution done
 
19
 
 
20
 
18
21
* settings                                                         :noexport:
19
22
# Local Variables:
20
23
# mode: org