Did i said already that i don't like how ASTInterpreter implemented? :) Nevertheless, it is useful.. and this case clearly demonstrates that. On 4 May 2013 00:14, Clara Allende <clari.allende@gmail.com> wrote:
This is great news! Are you going to publish the code? it will come in handy for my summer of code :D
Camillo has the image
On 3 May 2013 03:21, stephane ducasse <stephane.ducasse@free.fr> wrote:
Begin forwarded message:
From: Camillo Bruni <camillobruni@gmail.com> Subject: [Lsehub-staff] How to Debug :D Date: May 2, 2013 6:22:06 PM GMT+02:00 To: RMoD private list <lsehub-staff@lists.gforge.inria.fr> Reply-To: RMoD private list <lsehub-staff@lists.gforge.inria.fr>
Igor: Camillo can you help me debugging this strange athens rendering bug Cami: sure
Igor: where do you think the bug is? The green path jumps if I change the Y coordinate and it shouldn't... Cami: no clue...
Igor: Any clue how to get to the bug? Cami: let's use the ASTInterpreter to interpret two methods with different transformation matrices and see when they diverge.
Result: ------- - after 1h comparing AST Debugger is ready - we run the two traces, they do NOT diverge => ????
Conclusion: ----------- Cairo, which was chosen as reference, did not properly draw the path!!!
So we should publish the code of the ComparingInterpreter a bit and we can use it for a few more tasks in Pharo ;)
-- Best regards, Igor Stasenko.