|
I started with C and did that until that job went away, found the job with Delphi and did that job until it too played out (DoD decided they didn't want the system anymore). I wasn't looking for more Delphi but those skills got me into the current job which eventually changed projects to working in java.
All that to say this;
If someone wanted to pay me more to do Delphi than my current job pays, yes I would.
If someone wanted to pay me more to do old school C than my current job pay, yes I would.
If someone wanted to pay me more to clean up after elephants, I probably would.
I program to live, not live to program. It just pays the bills real good.
|
|
|
|
|
That's an honest answer, which makes me think of:
Quote: Honesty is such a lonely word
Everyone is so untrue
Honesty is hardly ever heard
And mostly what I need from you
|
|
|
|
|
This issue came up elsewhere in the Lounge[^] a couple of weeks or so ago and the response referred to using the $exception variable in Watch, without the need to define an exception in the catch statement: StackOverflow[^]
|
|
|
|
|
Like any normal person: Completely ignoring them! 
Anything that is unrelated to elephants is irrelephant
Anonymous
-
The problem with quotes on the internet is that you can never tell if they're genuine
Winston Churchill, 1944
-
Never argue with a fool. Onlookers may not be able to tell the difference.
Mark Twain
|
|
|
|
|
Depends on the code, sometimes I am intending to do something a bit odd.
|
|
|
|
|
Run it through a code analyzer to get more of them!
|
|
|
|
|
In my own code, I like to clean them all up. When compiling packaged software, say the latest version of gcc, I just do the configure/make/make install and ignore the warnings.
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.
|
|
|
|
|
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
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
