As seen in #191, the actual problem is not about the parameter, but a bug happening before that in the visitor.
I think we could improve the robustness of VerveineJ if we had a catch of exceptions during the visit of a node to print the stack of the error BUT resume the executing with the next nodes.
Like this, if we encounter an error we have less missing information.
As seen in #191, the actual problem is not about the parameter, but a bug happening before that in the visitor.
I think we could improve the robustness of VerveineJ if we had a catch of exceptions during the visit of a node to print the stack of the error BUT resume the executing with the next nodes.
Like this, if we encounter an error we have less missing information.