Skip to main content

Use content assist with Explicit type argument in Java compliance level 1.7



I'm using Eclipse 3.7 under Java 7, so I want to keep my compiler compliance level in 1.7.





By the way, I'm working together with people who use Eclipse 3.6 (which one does not support compliance level 1.7). So although my JRE is JavaSE-1.7, it compiles codes with 1.6 compliance level.





The problem is, because the compiler under 1.7 does not support implicit type arguments (diamond), it marks error. For example:







List<String> list1 = new ArrayList<>(); // It's recommended in Java 7, but marked as error in Eclipse 3.6







So I hope to set content assist to insert explicit type arguments (old style) rather than implicit type arguments (current style).





Is there a way to change how the content assist works?


Comments

Popular posts from this blog

Slow Android emulator

I have a 2.67 GHz Celeron processor, 1.21 GB of RAM on a x86 Windows XP Professional machine. My understanding is that the Android emulator should start fairly quickly on such a machine, but for me it does not. I have followed all instructions in setting up the IDE, SDKs, JDKs and such and have had some success in staring the emulator quickly but is very particulary. How can I, if possible, fix this problem?

Java Urban Myths

Along the line of C++ Urban Myths and Perl Myths : What are the Java Urban Myths? That is, the ideas and conceptions about Java that are common but have no actual roots in reality . As a Java programmer, what ideas held by your fellow Java programmers have you had to disprove so often that you've come to believe they all learned at the feet of the same drunk old story-teller? Ideally, you would express these myths in a single sentence, and include an explanation of why they are false.