Comments on: A Syntax Trick I Was Not Aware Of http://stuffthathappens.com/blog/2007/11/07/a-syntax-trick-i-was-not-aware-of/ Technology and Geek Stuff by Eric Burke Sat, 27 Feb 2010 14:52:46 -0500 http://wordpress.org/?v=2.8.6 hourly 1 By: Fred http://stuffthathappens.com/blog/2007/11/07/a-syntax-trick-i-was-not-aware-of/comment-page-1/#comment-1330 Fred Mon, 12 Nov 2007 22:33:15 +0000 http://stuffthathappens.com/blog/2007/11/07/a-syntax-trick-i-was-not-aware-of/#comment-1330 After reading all this energy to save inference, I wrote an entry to save Explicit Type Parameters ;-) The Ugly Duckling of Java! After reading all this energy to save inference, I wrote an entry to save Explicit Type Parameters ;-)
The Ugly Duckling of Java!

]]> By: Bob Lee http://stuffthathappens.com/blog/2007/11/07/a-syntax-trick-i-was-not-aware-of/comment-page-1/#comment-1161 Bob Lee Thu, 08 Nov 2007 22:17:42 +0000 http://stuffthathappens.com/blog/2007/11/07/a-syntax-trick-i-was-not-aware-of/#comment-1161 Yeah, no erasure here. Java just isn't smart enough to infer the generic types in method arguments. It's the classic chicken or the egg problem. The compiler needs to know the types of the arguments in order to decide which method to dispatch to, but it also needs to know which method it's dispatching to in order to infer the type parameters. Like Kevin said, it's tricky but doable, and it looks like this could be fixed in Java 7. Yeah, no erasure here. Java just isn’t smart enough to infer the generic types in method arguments. It’s the classic chicken or the egg problem. The compiler needs to know the types of the arguments in order to decide which method to dispatch to, but it also needs to know which method it’s dispatching to in order to infer the type parameters. Like Kevin said, it’s tricky but doable, and it looks like this could be fixed in Java 7.

]]> By: Fred http://stuffthathappens.com/blog/2007/11/07/a-syntax-trick-i-was-not-aware-of/comment-page-1/#comment-1116 Fred Thu, 08 Nov 2007 06:23:37 +0000 http://stuffthathappens.com/blog/2007/11/07/a-syntax-trick-i-was-not-aware-of/#comment-1116 It looks strange at first (some says very ugly) but Neal's use it all the time. I found out that it has good logic and solves some issue with Genric woodoo magic. For example in JPA: "MyBean = em.find(MyBean.class,pk);" In Java 5, the casting disappear automatically with no apparent reason. And if you want to hide implementation class and make users use only interface, it does not work anymore. So, "MyBean = em.<MyBean>find(persistentClass, pk);" solves the problem. It looks strange at first (some says very ugly) but Neal’s use it all the time.
I found out that it has good logic and solves some issue with Genric woodoo magic.
For example in JPA:
“MyBean = em.find(MyBean.class,pk);”
In Java 5, the casting disappear automatically with no apparent reason. And if you want to hide implementation class and make users use only interface, it does not work anymore.
So,
“MyBean = em.<MyBean>find(persistentClass, pk);”
solves the problem.

]]> By: Kevin Bourrillion http://stuffthathappens.com/blog/2007/11/07/a-syntax-trick-i-was-not-aware-of/comment-page-1/#comment-1110 Kevin Bourrillion Thu, 08 Nov 2007 04:02:28 +0000 http://stuffthathappens.com/blog/2007/11/07/a-syntax-trick-i-was-not-aware-of/#comment-1110 Annoying, isn't it. It's not to do with erasure, it's just a weakness in the language; but Neal has said it's fixable. You shouldn't have to either supply that <String> or use a temp var. Annoying, isn’t it.

It’s not to do with erasure, it’s just a weakness in the language; but Neal has said it’s fixable. You shouldn’t have to either supply that <String> or use a temp var.

]]>