Community
Participate
Working Groups
I have reproduced the following on both Linux and Win2k installation of Eclipse 3.1 When entering the following code (or similar) Eclipst tries to access the context content help if one enters a 'dot' after an enum variable (eg, after MyEnumVar) and never 'comes back' - one chan hear it accessing the hard disk continuously but no amount of waiting will do. The only resort is to 'kill' Eclipse and restard. Although I am aware this is not intended and only the result of mis-typing, it should not cause such a dramatic failure (especially as the ',' key - a natural thing to enter in a list of enums - is just next to the '.' key - a not so natural thing to type, admittedly) and might cause a significant amount of typing to go to waste. I have a feeling this is due to nested recursive calls when trying to resolve types. Code example: public enum MyEnum { MyEnumVar("myvar"), // enter dot here -^ AnotherEnumVar("anothervar"); private MyEnum(String s) { this.value = new String(s); } private final String value; public String value() { return s; } } the code otherwise compiles and works.
Just re-looked at the code - I realise that it should have been: public String value() { return value; } not that it makes any difference anyway. M
Closing as a dup of bug 107580. Please reopen if you get it again with either 3.2M2. *** This bug has been marked as a duplicate of 107580 ***