|
Quote: ISTR a story about the linux kernel, long ago, where some helpful individual went through the code and cleaned up all the warnings. Which was great, until you tried to compile it for something other than an X86 - in which case either the build failed or the kernel broke It was already broken.
|
|
|
|
|
|
I'm very OCD about warnings and even add checking for a dozen more obscure ones. I then pass my code through various analyzers.
Many times, seemingly trivial warnings exposed more serious logical errors.
|
|
|
|
|
warnings from the compiler only proves to me the compiler doesn't understand my code.
Message Signature
(Click to edit ->)
|
|
|
|
|
If the compiler doesn't understand your code, what chance do your co-workers stand...?
|
|
|
|
|
Have you ever heard of "Job Security" ?
Ravings en masse^ |
---|
"The difference between genius and stupidity is that genius has its limits." - Albert Einstein | "If you are searching for perfection in others, then you seek disappointment. If you are seek perfection in yourself, then you will find failure." - Balboos HaGadol Mar 2010 |
|
|
|
|
|
|
Lazy programmers might be the first ones that get fired...
|
|
|
|
|
You need to think deeper.
If a programmer is lazy, no production means no one remembers any bugs in their software or any other problems - because they've never run anything of theirs. They'll be held onto the longest as they never make any mistakes!!
Ravings en masse^ |
---|
"The difference between genius and stupidity is that genius has its limits." - Albert Einstein | "If you are searching for perfection in others, then you seek disappointment. If you are seek perfection in yourself, then you will find failure." - Balboos HaGadol Mar 2010 |
|
|
|
|
|
If you have a moment or two, could you please translate this into plain, proper English?
|
|
|
|
|
The English is plain enough.
You just need to reorganize you thought processes to consider more options than simply being logical.
Ravings en masse^ |
---|
"The difference between genius and stupidity is that genius has its limits." - Albert Einstein | "If you are searching for perfection in others, then you seek disappointment. If you are seek perfection in yourself, then you will find failure." - Balboos HaGadol Mar 2010 |
|
|
|
|
|
Well, maybe than it wasn't English in the first place.
And programming is all about being logical, and that includes proper treatment of compiler warnings...
And trust me, even after 43 years of programming, my thought process is just fine...
|
|
|
|
|
Compiler warnings fail our build. If we really need to ignore a specific warning, we disable it.
/ravi
|
|
|
|
|
set warnings as errors.
#SupportHeForShe
Government can give you nothing but what it takes from somebody else. A government big enough to give you everything you want is big enough to take everything you've got, including your freedom.-Ezra Taft Benson
You must accept 1 of 2 basic premises: Either we are alone in the universe or we are not alone. Either way, the implications are staggering!-Wernher von Braun
|
|
|
|
|
Warnings have the tendency to hide errors.
John Carmack wrote a pretty good article a few years ago about the best way to think of and treat warnings.
My plan is to live forever ... so far so good
|
|
|
|
|
While prototyping, who cares. When making the code production-ready, same as errors.
|
|
|
|
|
We ignore all warnings and catch bugs in user alpha testing.
Of course.
|
|
|
|
|
markrlondon wrote: catch bugs in user alpha testing.
Finally, a real-world answer!
If it weren't for users, I'd have no bugs at all.
"Go forth into the source" - Neal Morse
|
|
|
|
|
I don't take threats!
Ravings en masse^ |
---|
"The difference between genius and stupidity is that genius has its limits." - Albert Einstein | "If you are searching for perfection in others, then you seek disappointment. If you are seek perfection in yourself, then you will find failure." - Balboos HaGadol Mar 2010 |
|
|
|
|
|
We manage them. Warnings which disturb us (coding-style variances those warn us of, mostly) get disabled by the ruleset, merging anything is only possible with zero warnings. Too often have warnings led to bugs, and managing them to get only those which add value for our team has suited us well.
I only have a signature in order to let @DalekDave follow my posts.
|
|
|
|
|
I consider them Errors and fail the compile.
|
|
|
|
|
I prefer to call them suggestions. and if I wanted suggestions for my code, I'd just out-source it.
CQ de W5ALT
Walt Fair, Jr., P. E.
Comport Computing
Specializing in Technical Engineering Software
|
|
|
|
|
To the knife.
Software Zen: delete this;
|
|
|
|
|
Compiler warnings should never be ignored. If you ignore them, they build up and eventually obscure things like: "Unable to resolve reference to x as it was built with a higher framework version". This is just a warning, but try and publish such an application and you will quickly find it does not work in production. The number of times I am asked to help someone solve an issue which they could have solved themselves if they just read the warnings...
|
|
|
|
|
The only warnings ones I (usually) have are "returns" used to "disable" code meant for (eventual) deletion. So, I guess I do take notice when it's something else. They eventually get cleaned up; mostly unreferenced variables. Probably an OCD thing.
(Someone once noticed I had left an unused namespace in my XAML ... while I was developing; and felt they needed to bring it up).
The Master said, 'Am I indeed possessed of knowledge? I am not knowing. But if a mean person, who appears quite empty-like, ask anything of me, I set it forth from one end to the other, and exhaust it.'
― Confucian Analects
|
|
|
|