Community
Participate
Working Groups
Using 3.1 M3. Open this bug to complete fix done for bug 77538. When node parent's change while moving and new parent's node is still original, then extended positions for node will be wrong as it is computed using parent's extended ones... I attach the patch to this bug which is a starting point for this bug fix but need more investigation to: 1) verify that it's not too much time consuming 2) pass specific DefaultCommentMapper tests
Created attachment 15610 [details] Starting point to fix this issue
Fixed. Instead of storing { -1, -1 } for range of node needing parent extended position, compute directly extended position for children when an extended is found for a node. This new algorithm has the advantage to remove all unnecessary entries when parent has in fact no extended position... Also change HashMap for arrays to stores leading and trailing ranges and nodes to minimize storage and time execution. [jdt-core-internal] Changes done in DefaultCommentMapper. Test case added in ASTConverterJavadocTest
Verified in 200412140800