Description Maxime Daniel 2006-06-26 11:01:06 EDT

v_702

This is a fup of bug 102728.
BinaryExpressionFragmentBuilder#visit(BinaryExpression, BlockScope) implements its own traversal of binary expressions. As such, it bypasses the safer traversal put in place with CombinedBinaryExpression, hence tends to hit the stack bottom before the 64K limit on method bodies is reached (typically, it takes about six times shorter strings concatenations to break the formatter than it takes to hit the 64K limit).
Two possible tracks would be to:
- rely upon the regular traversal, hence leveraging CombinedBinaryExpression
  without being aware of it;
- recode the custom traversal so as to explicitly leverage   
  CombinedBinaryExpression and lower the traversal requirements on the stack.