This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
[Reported by Bill Sutherland <wsutherland@freeuk.com>] Hello Tomas. I've attached an example class that I think shows up the problem. If you first use the IMT to look at the way symbols have been resolved with the for block commented out and then un-comment the for block and look again, you'll see (I hope) that you don't get the same picture. If you "Finish" the IMP with the for block un-commented then you get problems compiling, or at least I did. You can compile the code by commenting out the for block, using the IMT to resolve everything, and then un-comment it again, so there is a work-around, even if it's not a great one. Regards, Bill. p.s. The problem is reproducable on both HP-UX and Mac OS X platforms. I will attempt to raise an issue tomorrow but I don't have an ID yet.
Created attachment 5436 [details] Testcase
Ok, I found it. The bug is triggered only if there is another block (i.e. something in { .. }) inside initializer. So for example static { b = new File(); } is OK.
Fixed in trunk.
Verified in 200210090100
Resolved for 3.4.x or earlier, no new info since then -> closing.