Autoboxing

The objective of autoboxing is to simplify code and increase readability and, as such, is a welcome addition. ❋ Sebsto (2010)

· J2SE 5.0 "Tiger" Language Support - We support the new Java language constructs such as enums, generics, metadata annotations, autoboxing, static imports and others. ❋ Unknown (2010)

· Moved codebase to minimum of Java 5 for generics/autoboxing ❋ Unknown (2010)

How to run javac 1.5 (or beyond) compiler for JSP compilation in Tomcat 5.5 with generics enabled (and other Java 1.5 only features like autoboxing) ❋ Unknown (2010)

To me this means autoboxing such that you can call a mutating sub with a constant. ❋ Unknown (2009)

And since C# provides autoboxing, you can assign anything you want to this variable. ❋ Unknown (2008)

This in turn motivated autoboxing, a solution to the syntax problem that I consider to be yet another code smell. ❋ Unknown (2008)

I also wish we'd found some way to make generics work with primitive types, so that we could have avoided autoboxing and auto-unboxing, which have proven bug prone. ❋ Unknown (2008)

The improvements include annotations, generics, enums, autoboxing, variable number of arguments and static imports. ❋ Unknown (2008)

In it, he talks about the folly of premature optimization, writing your own libraries instead of using what's already out there, strange things in Java and undesirable side-effects of signed bytes and of autoboxing, Java's complexity budget, the future of Java, and more. ❋ Unknown (2008)

I've been fixing a lot of bugs wrote up how I fixed autoboxing primitives in MMD fixed at least one segfault for Will, have more to look at also fixed a couple of memory leaks the default PIR programs now should never leak any memory but IMCC still leaks memory in some cases will continue to fix any segfault reproduced as nicely as Will has done spent most of this week trying to reduce several thousand lines of Tcl into a small PIR program so I could get past a segfault ❋ Unknown (2008)