Howard Lewis Ship is another on the list of “frustrated with generics”.
I totally agree. If we were going to REALLY go generic, then we should have bite the bullet and made all of the changes, especially so we didn’t have runtime erasure.
As someone said, all you need to do is look at the JavaDoc and see something like:
public abstract class Enum<E extends Enum<E>>
Greeeeat. Explain that to the average Java Joe.
We get compile time checking, and we make everything thrice as complicated in the mix. Is that good? Seeing Map<String> looks good and all, and then you get into writing generic code and you scream.
July 8th, 2005 at 1:29 pm
For an explanation read this: http://madbean.com/2004/mb2004-3/
July 8th, 2005 at 1:33 pm
Hi Dion,
Compare this to say, WTL’s complexity(aka ATL — http://www.microsoft.com/resources/sharedsource/Licensing/WTL.mspx)
and then you will come away happy :-)
Happiness is relative — exponsing oneself to a lil more complex stuff from MS can make one happy(ier)!
BR,
~A
July 14th, 2005 at 2:28 pm
When is the first book specifically on Java Generics going to appear? This thing needs a well-written book to grasp and try out.
For that matter, when is a book specifically on Concurrency Tiger Style going to appear?
May 7th, 2007 at 5:14 am
why we r going abstarct class in java
October 8th, 2007 at 12:15 pm
anime
October 8th, 2007 at 12:15 pm
anime