Oh thanks you so much!
In fact you can't design a Object like "standard" language with members, methods,... but you store it in a kind of structure where an index represent a member, in fact an array.
Now i understand what you were meaning by storing an object.
But i'm still thinking about the design of your solution.
Your solution seems like that right?
(the content is given for example)
[0][0]=0.2 (in second for timestamp)
[1]="T"
[1][0]=0.5 (in second for timestamp)
[1]="LR"
[2][0]=0.9 (in second for timestamp)
[1]="T"
[3][0]=1.2 (in second for timestamp)
[1]="D"
I don t understand the need of the index of obstacle and how to know on what index the system is
Would not it be better to use embeded condition "Every 0.1s" Add 1 to a variable that represent Array index and make an array like :
[0]=""
[1]=""
[2]="T"
[3]=""
[4]=""
[5]="LR"
[6]=""
[7]=""
[8]=""
[9]="T"
[10]=""
[11]=""
[12]="D"
?
Anyway thanks you for explanations!
Edit : An array always begin at 0.
As we say in French : "Les geeks n'ont pas une case en moins ils commencent juste ? partir de 0"