|Version 6 (modified by fbatard, 5 years ago)|
Correct repetitive bugs in Unicorn Call
We had to rebuild the whole dependance things with the classes
We had to correct the algorithm and think about the Response.
Does the if launch an observation or does it use a result previously executed?
I mean , the if does an observation or use an previous observation done by an exec?
The answer to this question will completly change the data structure and the algorithm to apply the condition in UnicornCall?.
Then we debate about that.
If the if doesn't perform an observation we'll just need of map of Response with the name of the observer as an ID.
Therefore the condition of the if will give us the name of the observation on which we'll have to apply the condition and we can search it in the map of Response.
Otherwise it's a little bit trickier to get the observer of the if to launch it but still possible.
We'll have a huge map of Response which will group all the response. This map will be filled thanks to the recursion on the tree.
We may have erased more mimetypes occurence than needed. Then we deleted a bit of check concerning the mimetype in UnicornCall?.
Then we have to re write it.
We had to merge the version of Johnathan with mine , with minor problems... just took ages to do for each class.