Join GitHub today
Exceptions are reported every time they propagate up in the call chain in the ruby debugger #26
This is the scenario:
Effect: the IDE shows the exception and offers to stop on that exception. If this is declined, the exception will be propagated upwards in the call chain. Every time, the exception is raised on the next level in the call chain, the IDE will again offer to stop. This becomes tedious if many levels are involved.
The problem only happens when the exception is propagated through an iteration loop of KLayout's objects. Here is an example:
poly = RBA::Polygon::new(RBA::Box::new(0, 0, 100, 100)) poly.each_edge do |e| raise "some exception" end
The exception is reported twice: once when it's thrown and a second time when it is propagated through the "each_edge" iterator.