diff options
| author | Dieter Plaetinck <dieter@plaetinck.be> | 2008-11-02 22:52:11 +0100 |
|---|---|---|
| committer | Dieter Plaetinck <dieter@plaetinck.be> | 2008-11-02 22:52:11 +0100 |
| commit | 3b7d5576116b84b0062d995f00190d95481b0cfb (patch) | |
| tree | 80305bba649c78a439c6d4e09a2e136adb333acf /TODO | |
| parent | b506ebef3ec30e2cfc225833783ebed59b12524c (diff) | |
dont source procedures for each loaded module. dont auto source core/base either. we now have a dependency system for procedures
Diffstat (limited to 'TODO')
| -rw-r--r-- | TODO | 5 |
1 files changed, 3 insertions, 2 deletions
@@ -10,8 +10,9 @@ other steps warning 'not implemented' we should have even more flexibilty to take parts from different procedures. eg dieter procedure maybe wants to use something interactive. or base procedure wants to do something interactive. interactive functions maybe - dont belong in a procedure? - + dont belong in a procedure? -> depend_procedure good enough? or do we + need more fine-grained dependencies (take function foo from procedure bar + from module baz). for now let's try like this.. * base procedure idea: it should just tell you what to do? -> less implementation work in base procedure, more in other procedures... * fix crossconcerns: procedures are about _how_ (autodetection, asking user,...) |