RE: [cdt-dev] building the Memory Browser and Traditional Renderer

[John Cortell <rat042@xxxxxxxxxxxxx>]

Thanks, Randy. I can tell you for sure Java warnings are not just
informational, though some warnings for sure are ones you want to tell
the compiler "I know what I'm doing; leave me alone", and
that's what the @SuppressWarnings is for. 

A month or so ago I found something like this in some Java code.

if (someBool = true) {
   doSomething();
}

It had been there for quite some time. The compiler had been trying to
tell us all along that we had made a bonehead coding error, but it fell
on deaf ears because the warning was drowned out by hundreds of other
warnings. The cost of Freescale finding this out because of a runtime
issue reported by a customer vs finding it at build time differs in cost
by orders of magnitude, I'm sure. Thus my interest in keeping code as
clean as possible.

John


At 03:07 PM 5/10/2010, Rohrbach, Randy wrote:

Content-Class: urn:content-classes:message
Content-Type: multipart/alternative;
         boundary="----_=_NextPart_001_01CAF07C.7B4D4570"

John
 
   By the way I agree with the philosophy of "0" warnings. Not so much in JAVA but
   certainly in other languages I have been burned badly by warnings. Ignore them at
   your peril. When I first started working on DSF and JAVA I got the advice that JAVA
   warnings are never fatal or bad just informational. But I have just not been able to
   shed the OLD SCHOOL mentality of mine.
 
   So thanks for the effort here. I spent alot of time getting rid of a lot of warnings in DSF
   but they keep coming back for more.
 
Randy

---

From: John Cortell [ mailto:rat042@xxxxxxxxxxxxx]
Sent: Monday, May 10, 2010 3:46 PM
To: CDT General developers list.; CDT General developers list.
Cc: Rohrbach, Randy
Subject: Re: [cdt-dev] building the Memory Browser and Traditional Renderer

Yes. I sent various emails on the subject. It's my belief that our plugins should generate zero warnings, and the memory projects have been set up to try to ensure that (now that i removed all warnings). Whatever warnings (now errors) you are seeing should  be fixed, not ignored. One such issue was reported this morning and fixed, and it was due to a subtle difference between Canvas on linux and Windows that I was not seeing. I'll be happy to investigate and fix any other issue you are seeing.

John


At 02:40 PM 5/10/2010, Rohrbach, Randy wrote:

Content-Class: urn:content-classes:message
Content-Type: multipart/alternative;
         boundary="----_=_NextPart_001_01CAF078.A75F9926"

Folks
 
   I just updated my Open Source Reference CDT developmemnt space to all M7.
 
   I needed to reset the build options errors/warnings for the MemoryBrowser and
   TraditionalRenderer to the defaults in order to get them to build. I have not made
   any changes to these components. There were certain specifications which were
   forcing errors where they used to just be warnings.
 
   I have seen some emails ( but not followed to closely ) concerning errors and
   warnings changes.
 
   Has anything been changed for these components.
 
   Thanks for the info.
 
Randy
_______________________________________________
cdt-dev mailing list
cdt-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cdt-dev

_______________________________________________
cdt-dev mailing list
cdt-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cdt-dev