boxing/unboxing/autoboxing
hi guys
I would like to have some information about what is boxing/unboxing/autoboxing
Interms of application performance is it good to use them or avoid them?
How is this related to generics in java?
A simple and clear answer would be greatly appreciated
thanks
I would like to have some information about what is boxing/unboxing/autoboxing
Interms of application performance is it good to use them or avoid them?
How is this related to generics in java?
A simple and clear answer would be greatly appreciated
thanks
Last Comment
One of the examples in there shows how it is related to generics
Consider the following example: if we want to store an int “a” into vector “vt”, we have to use wrapper class. And if we want to get element stored at position “0” of vector “vt”, we again have to do casting.
int a = 10;
Vector vt = new Vector();
vt.add(new Integer(a));
int n = ((Integer)vt.elementAt(0)).intValue();
J2SE 5.0 has made this easy. If we want to do the same in Java 5, the code will be like:
int a = 10;
Vector <integer> vt = new Vector <integer> ();
vt.add(a);
int n = vt.elementAt(0);
ASKER CERTIFIED SOLUTION
THIS SOLUTION IS ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
ASKER
>>>Vector <integer> vt = new Vector <integer> ();
shouldnt it be Vector <Integer> vt = new Vector <Integer> ();
with a capital I
shouldnt it be Vector <Integer> vt = new Vector <Integer> ();
with a capital I
SOLUTION
THIS SOLUTION IS ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
I would think it should be capital, they probably have a miosprint
> Interms of application performance is it good to use them or avoid them?
avoid it.
All its doing is create a wrapper Object for you. And too much Object creation is going to hurt the performance of your application.
avoid it.
All its doing is create a wrapper Object for you. And too much Object creation is going to hurt the performance of your application.
ASKER
>>> So boxing and unboxing too many values can make garbage collector go wild. Hence it is not a advisable to use autoboxing and unboxing for scientific computing, or other performance-sensitive numerical code as it will affect the performance to a good extent.Using primitive types will better serve the purpose there.
We could not use primitive types directly to add to a Collection and that is why they came out with autoboxing/unboxing. so i dont understand what they mean by
>>Using primitive types will better serve the purpose there.
We could not use primitive types directly to add to a Collection and that is why they came out with autoboxing/unboxing. so i dont understand what they mean by
>>Using primitive types will better serve the purpose there.
Of course all complications apply if you have huge amounts of data.
If you have arrays data in hundreds and maybe not too big thousands convenience is of couse more important and you can do
it as conevenient for you to prorgram
When it goes to big numbers then you should become cautious.
If you have arrays data in hundreds and maybe not too big thousands convenience is of couse more important and you can do
it as conevenient for you to prorgram
When it goes to big numbers then you should become cautious.
> We could not use primitive types directly to add to a Collection and that is why they came
> out with autoboxing/unboxing. so i dont understand what they mean by
thats not really why they came out with autoboxing. Its just "syntactic sugar". They don't allow you to do anytrhing you couldn't do previously, it just makes your code more concise
> out with autoboxing/unboxing. so i dont understand what they mean by
thats not really why they came out with autoboxing. Its just "syntactic sugar". They don't allow you to do anytrhing you couldn't do previously, it just makes your code more concise
Java
Java is a platform-independent, object-oriented programming language and run-time environment, designed to have as few implementation dependencies as possible such that developers can write one set of code across all platforms using libraries. Most devices will not run Java natively, and require a run-time component to be installed in order to execute a Java program.
102K
Questions
--
Followers
--
Top Experts
Get a personalized solution from industry experts
TRUSTED BY
These are simple examples:
http://www.java-tips.org/blog/java-se/autoboxing-and-unboxing-in-java-5.html