The following document contains the listing of user tags found in the code. Below is the summary of the occurrences per tag.
Tag Class | Total number of occurrences | Tag strings used by tag class |
---|---|---|
@todo | 0 | @todo |
TODO | 23 | TODO |
Each tag is detailed below:
Number of occurrences found in the code: 23
cz.cuni.amis.pogamut.shady.IArgument | Line |
---|---|
Stub | 14 |
cz.cuni.amis.pogamut.shady.NodeCall | Line |
How is target determined. Probably search in order: node names, names on classpath, fqn names of classes. | 14 |
cz.cuni.amis.pogamut.shady.QueryCall | Line |
explain, how target is determined | 13 |
cz.cuni.amis.pogamut.shady.ShadeEngine | Line |
this would not work at all!!! | 108 |
cz.cuni.amis.pogamut.shady.ShadyParser | Line |
what about variables? | 280 |
cz.cuni.amis.pogamut.sposh.PoshTreeEvent | Line |
Not enough info, where was it before? | 18 |
cz.cuni.amis.pogamut.sposh.elements.ActionPattern | Line |
Unify with rename in competence | 307 |
rollback if some error happens? | 333 |
cz.cuni.amis.pogamut.sposh.elements.Arguments | Line |
This probably doesn;t need to be abstract list | 20 |
cz.cuni.amis.pogamut.sposh.elements.Competence | Line |
Somehow unify with ActionPattern one. | 284 |
rollback if some error happens? | 309 |
cz.cuni.amis.pogamut.sposh.elements.Result | Line |
Maytbe reuse the parser instead of duplicating the code | 94 |
cz.cuni.amis.pogamut.sposh.elements.Sense | Line |
Correctly document, changed in hurry. This is not correct,. we just call PoshParser Take the input that represents the sense in one way or another and set this sense to the values found in the input. | 308 |
cz.cuni.amis.pogamut.sposh.elements.TriggeredAction | Line |
Check that all variables used as values in the newArguments are present in the parameters of parent, use getParentParameters(). | 139 |
cz.cuni.amis.pogamut.sposh.engine.APExecutor | Line |
Is this even needed? SURFACE fo all should be sufficient. | 38 |
cz.cuni.amis.pogamut.sposh.engine.CExecutor | Line |
What should I do with goal of competence? It would be best to remove it completely. | 89 |
cz.cuni.amis.pogamut.sposh.engine.DEExecutor | Line |
optimalize by pre-caching indexes of adapts/competences on the stack CHECK FOR COMPETENCES/ADAPTS GOALS/EXIT-CONDITIONS FIRST!!! | 72 |
cz.cuni.amis.pogamut.sposh.engine.INodeExecutor | Line |
Once confirmed that same, replace driveId | 84 |
Remove and do some other way | 90 |
Remove later, this translation is to keep somehow compatible with tests | 137 |
Implement | 190 |
In original #driveInterrupted, it cleared up to first occurance of ADExecutor | 245 |
cz.cuni.amis.pogamut.sposh.engine.PoshEngineTest | Line |
Retries in CEExecutor don't work because the executor is always unwinded. Remove them? | 452 |