Nope. The code does run.
The correct answer is: Conference [Herman, Bobby, Robert]. So far, only
1624/9303 (17%) got that right!
The compiler does not find a remove(int) method on the Collection interface, so it
autoboxes the int to an Integer. Generics would also not have helped, since the
remove method takes an Object as a parameter.
Sign up now for our Java 5 Tiger course, where you
will see lots of other tricks like this and how to avoid this bug in your code.
Prerequisites for the Tutorial
You should be very comfortable with Java 1.4 code and have a
good understanding of your IDE. Please bring along a
laptop with JDK 1.5 preinstalled.
"The course is presented in a very good way. There are
lots of exercises, the teacher knows what he is talking
about and is ready to answer questions."
- Wolfgang R. Alcatel, Austria
Tutorial Outline - Migration
from Java 1.3/1.4 to Java 5.
Chapters and Descriptions
- Introduction to Tiger - History of Java,
most significant changes, overview of tutorial
- Annotations - @Override, @Deprecated,
@SuppressWarnings, Writing your own, Extracting with
reflection
- Generics - Using generics,
java.lang.Comparable, wildcards, extending generic classes,
for/in loop, erasure and other complaints
- Autoboxing Boxing, when to use, when to
avoid, performance considerations
- Enum - Defining simple enums, complex
enums, adding methods, generated enum code, switching on enums
- Static Imports - How to use, when to
avoid, combining with Enum.
- New collections - Queue, BlockingQueue and
implementations, writing safer concurrent code, TimeUnit
- Variable Arguments - Examples in the JDK,
how it works, generated code
- Bonus Features - Bit manipulation in Tiger,
central exception handling, management beans for deadlock
detection and memory monitoring.
Contact up now for a Java 5 course.
|
