Eclipse Community Forums: Java Development Tools (JDT)

Help

Home

Home » Language IDEs » Java Development Tools (JDT) » Boxing Compiler Warnings

Show: Today's Messages :: Show Polls :: Message Navigator

Boxing Compiler Warnings [message #664588]

Mon, 11 April 2011 09:57

Thomas Schindl

Messages: 6651
Registered: July 2009

Senior Member

Hi,

I've been hit by NPEs in code produced by my co-workers and found the
compiler option "Java > Compiler > Error/Warnings >
Potential programming problems > Boxing and unboxing conversions".
Setting this one to a "Warning" adds the warnings whenever you type:

int i = o.getInteger(); // Bla#getInteger(): Integer

but also if you do:

o.setIntger(10); // Bla#setInteger(Integer): void

Is there an option I missed which adds a warning when a conversion from
the object to the primitive type is happening (which is a potential
programming problem) but in the opposite case?

Tom

Report message to a moderator

Re: Boxing Compiler Warnings [message #664654 is a reply to message #664588]

Mon, 11 April 2011 13:53

Eclipse User

Originally posted by: richkulp.us.NOSPAM.ibm.com

Hi,
>
> o.setIntger(10); // Bla#setInteger(Integer): void
>

I'm not sure if I understand correctly. But it is not physically
possible to have an NPE going from from a primitive->Object. There is no
such thing as a null primitive value so you will always get an instance
of Integer (assuming going into an Integer) and never a null.
--
Thanks,
Rich Kulp

Report message to a moderator

Re: Boxing Compiler Warnings [message #664655 is a reply to message #664654]

Mon, 11 April 2011 14:02

Thomas Schindl

Messages: 6651
Registered: July 2009

Senior Member

Am 11.04.11 15:53, schrieb Rich Kulp:
> Hi,
>>
>> o.setIntger(10); // Bla#setInteger(Integer): void
>>
>
> I'm not sure if I understand correctly. But it is not physically
> possible to have an NPE going from from a primitive->Object. There is no
> such thing as a null primitive value so you will always get an instance
> of Integer (assuming going into an Integer) and never a null.

Exactly and that's why a warning on this line is NOT making sense
whereas on the opposite it does.

So my request is:
a) Get a new prefernce where only Object => Primitive is flagged with a
warning
b) Modify the current warning to only Object => Primitive leads to a
warning

Tom

Report message to a moderator

Previous Topic:	How to Modify the Eclipse Java Compiler/Grammar java.g. has any introducts the grammar of .g file?
Next Topic:	How to add custom validation?

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

]

Current Time: Fri Apr 26 02:22:55 GMT 2024

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter