Community
Participate
Working Groups
M20050824-1200 See JDT/Core bug 104293. For that specific instance of the problem, there's an easy workaround in JdtASTMatcher that we should submit for 3.1.1.
Created attachment 26527 [details] Fix
Created attachment 26528 [details] Regression Tests
Tobias & Dirk, please review for 3.1.1.
Patch looks good, +1 for 3.1.1
Using Bindings.equals requires node.resolveBinding() not being null. This wasn't the case before. Markus, can you please improve the patch.
Created attachment 26579 [details] Better fix Duh, stupid me. Here's a better fix.
Created attachment 26580 [details] Better Tests Tests, including test for comment 5.
Created attachment 26581 [details] Better fix 2 Selected wrong file before :-(
Created attachment 26582 [details] Better fix 3 3rd try to submit the better fix (it's monday morning;-)
Patch looks ok to me. For 3.2: doesn't it make sense to say that the two nodes are equal if we don't have bindings for them. I would opt to return false in this case as well.
Tobias, could you please review the latest fix again? > For 3.2: doesn't it make sense to say that the two nodes are equal if we don't > have bindings for them. I would opt to return false in this case as well. Yes, I agree it would make sense to consider nodes without bindings as equal (and return _true_ in that case). I'll file a new bug for that and fix it in HEAD after having tested this fix for a while.
Patch looks ok to me
Released patches to HEAD and 3.1.1 branch. The other bug is bug 108354.
Verified using M20050831-1200 + ZRH plugin export