Comments on: JDK 5 – auto-boxing best practices

By: Tile Bathroom

Tile Bathroom — Thu, 29 Dec 2011 16:39:41 +0000

Normally I do not learn post on blogs, but I would like to say that this write-up very pressured me to take a look at and do it! Your writing style has been amazed me. Thank you, quite great article.

By: Manny Pacquiao trains with Freddie Roach | boxing-fights.info

Manny Pacquiao trains with Freddie Roach | boxing-fights.info — Tue, 20 Sep 2011 11:43:03 +0000

[...] JDK 5 – auto-boxing best practices | Invert Your Mind – Just wanted to discuss quickly a few simple best practices for auto-boxing in Java. This will help prevent shooting ones self in the foot. If you can use primitives do it, if you can't don't. [...]

By: Frank Bruno becomes World Champion | boxing-fights.info

Frank Bruno becomes World Champion | boxing-fights.info — Sat, 10 Sep 2011 15:04:07 +0000

By: liam

liam — Mon, 19 Jul 2010 20:18:56 +0000

My problem with the ternary logic is that you are assuming that null means zero.
My problem with unboxing is, aside from the performance hits and the hard-to-trace null pointer exceptions, less-seasoned developers are treating the wrapper classes like they are primitives, which means that someone has to go behind them and clean up.
With the need to do so much checking and tiptoeing around auto boxing an unboxing, it is still a mystery to me why they were introduced.

By: Chandra Watson

Chandra Watson — Thu, 13 Nov 2008 03:24:29 +0000

83rzx3ig751h7kbb

By: Brian Pontarelli

Brian Pontarelli — Wed, 17 Jan 2007 22:18:33 +0000

Sorry for the delayed response on this… Autoboxing happens anytime you call a method, assign a variable or otherwise cast the type from a primitive to a wrapper.

The best practice depends on your needs. If you need to have a null value, then declare your method with the wrapper, otherwise use a primitive.

By: dh

dh — Fri, 12 Jan 2007 14:13:31 +0000

I liked this post very much and felt it was very informing, and I just want to try and understand unboxing/boxing correctly.

Does boxing happen when you parse a primitive to a method?

ex. someMethod(int value){}

I’m just trying to figure out which is the best practice when creating methods/constructor, using primitives or wrapped primitives?

ex. MyClass(Integer id, Long value){}

vs.

ex. MyClass(int id, long value){}

Hmm not sure I formulated my question correctly, but alas english is not my native tongue, so bare with me.

btw. your site was the first hit on “java boxing unboxing best practice” on google

By: Wes Maldonado: Data Junkie » Blog Archive » Java 1.5 Autoboxing Links

Wes Maldonado: Data Junkie » Blog Archive » Java 1.5 Autoboxing Links — Thu, 01 Jun 2006 20:11:35 +0000

[...] http://brian.pontarelli.com/2004/07/15/jdk-5-auto-boxing-best-practices/ [...]