#49 closed defect (done)
Remove operator reset mechanism
| Reported by: | swagner | Owned by: | swagner |
|---|---|---|---|
| Priority: | low | Milestone: | HeuristicLab 3.3.0 |
| Component: | Core | Version: | 3.0 |
| Keywords: | Cc: |
Description
The reset mechanism for operators is considered dangerous and should be removed. It may encourage users to implement operators with internal states (local variables) that are only valid for a single algorithm execution. This could be quite harmful as we saw in HeuristicLab 2.0. Instead, state variables should be stored in scopes. Local variables of operators should be valid throughout the whole life time of an operator which normally is longer than a single algorithm execution.
Change History (6)
comment:1 Changed 16 years ago by swagner
- Status changed from new to assigned
comment:2 Changed 16 years ago by gkronber
comment:3 Changed 16 years ago by swagner
- Resolution set to fixed
- Status changed from assigned to closed
Fixed in r47
comment:4 Changed 16 years ago by swagner
- Milestone changed from 3.0 to Iteration 0
Milestone 3.0 deleted
comment:5 Changed 14 years ago by swagner
- Milestone changed from Iteration 0 to Current
Milestone Iteration 0 deleted
comment:11 Changed 14 years ago by swagner
- Milestone changed from Current to HeuristicLab 3.3.0
Milestone Current deleted
Note: See
TracTickets for help on using
tickets.
Full ACK!