|
Size: 1340
Comment:
|
Size: 1340
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 10: | Line 10: |
| * Objects created by plug-ins: what should they be called? When do we need a factory, and when does the plug-in generate the object directly? How is there lifetime managed -- when should we use shared_ptr and when should we use raw pointer? | * Objects created by plug-ins: what should they be called? When do we need a factory, and when does the plug-in generate the object directly? How is their lifetime managed -- when should we use shared_ptr and when should we use raw pointer? |
Back to ForDevelopers.
Long term plans
use task interface everywhere (issue509)
remove preprocessor (issue26)
state representation (issue401)
life-time management of shared objects (e.g. CG) (related: issue564)
- rethink which shared objects can go together (e.g. when is it OK for a heuristic to use a different task than a search algorithm using it? When is it OK for a pattern selector to work with a different task? a landmark factory? an operator-counting constraint generator? etc.)
- Objects created by plug-ins: what should they be called? When do we need a factory, and when does the plug-in generate the object directly? How is their lifetime managed -- when should we use shared_ptr and when should we use raw pointer?
plugins for open lists (issue610)
- remove global objects
group code into namespaces and core (issue64)
new plugin types without code changes in option parser (issue588)
Needs tender love and care
- landmarks
- option parser
- search