Comments on: [Revised Opinion] JDK1.5 not so scary… but update those coding standards http://madbean.com/2003/mb2003-28/ Your zero step program Fri, 05 Sep 2008 16:59:12 +0000 http://wordpress.org/?v=2.5.1 By: Aditya http://madbean.com/2003/mb2003-28/#comment-366 Aditya Fri, 22 Jul 2005 09:29:50 +0000 http://madbean.com/blog/2003-28#comment-366 <p>jdk1.5 shifts the responsibility of writing the boilerplate code from the programmer to the compiler. So it far sure that chances of mistake would be less. New features like generics will take some time for adjustment of developers especially when mix of legacy and new code will happen. Enhanced for loop and Autoboxing/unboxing looks cool. Typesafe enums, Static import and up to some extent generics looks like as if java is moving towords its parent C++ :)</p> jdk1.5 shifts the responsibility of writing the boilerplate code from the programmer to the compiler. So it
far sure that chances of mistake would be less.
New features like generics will take some time for adjustment of developers especially when mix of legacy
and new code will happen.
Enhanced for loop and Autoboxing/unboxing looks cool.
Typesafe enums, Static import and up to some extent generics looks like as if java is moving towords
its parent C++ :)

]]> By: Matt Quail http://madbean.com/2003/mb2003-28/#comment-72 Matt Quail Mon, 13 Oct 2003 07:12:54 +0000 http://madbean.com/blog/2003-28#comment-72 <p>Yeah, I certainly like the "?" wildcards. <? extends Number> makes a whole lot of sense.</p> Yeah, I certainly like the "?" wildcards. <? extends Number> makes a whole lot of sense.

]]> By: Neal Gafter http://madbean.com/2003/mb2003-28/#comment-71 Neal Gafter Mon, 13 Oct 2003 07:08:36 +0000 http://madbean.com/blog/2003-28#comment-71 <p>Coding standards for variance (now wildcards). One big one: don't use them in return types just to express readonlyness of the result. That will force your client to store the result using a wildcard, which will force him to learn about them. Instead, reserve wildcards for the places where they simplify the signatures in an API.</p> <p>This principle was applied liberally between the 2.0 and 2.2 prototypes, with the result that the 2.2 prototype APIs are much easier to read and use than any previous version. I think if you look at them and try them (and just glance at the new syntax for wildcards - it's intuitive!) you'll be very pleased.</p> Coding standards for variance (now wildcards). One big one: don’t use them in return types just to express readonlyness of the result. That will force your client to store the result using a wildcard, which will force him to learn about them. Instead, reserve wildcards for the places where they simplify the signatures in an API.

This principle was applied liberally between the 2.0 and 2.2 prototypes, with the result that the 2.2 prototype APIs are much easier to read and use than any previous version. I think if you look at them and try them (and just glance at the new syntax for wildcards - it’s intuitive!) you’ll be very pleased.

]]>