Compiler Warnings...
-
How seriously do you handle them?
"The only place where Success comes before Work is in the dictionary." Vidal Sassoon, 1928 - 2012
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...
-
Have you ever heard of "Job Security" ?
"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
-
How seriously do you handle them?
"The only place where Success comes before Work is in the dictionary." Vidal Sassoon, 1928 - 2012
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
-
How seriously do you handle them?
"The only place where Success comes before Work is in the dictionary." Vidal Sassoon, 1928 - 2012
We are in the process of introducing the Coverity static code analyzer. It is very good at telling you why it warns you ("If [this] occurs, and then [this] and then [this], then you follow a null reference at [that] line" - the series of inferences may jump from source file to source file, and may go in five or six or more steps). For this discussion it is more important that it maintains a history of all the "defects": If you have once reported that a given defect is in intentional, at the next Coverity run it will not be reported again. Same if you have flagged it as a false warning (which may occur if you set the agressiveness level to "high"). So you won't have the same warnings again and again. That makes it much more realistic to handle even moderate risk defects, because you do it once only. And if you give it a verdict of "intentional" or "false warning", you can leave it in your source code as it is. Actually I am a little bit in love with Coverity at the moment. I never seen any compiler or other code analyzer that comes close to it neither in its ability to detect defects, nor its flexibility in handling them. The big disadvantage is that your billfold will complain loudly ... And it takes some heavy iron (or lot of patience). But when you employer can afford both the software and the iron, then it is great.
-
Have you ever heard of "Job Security" ?
"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...
-
Would you still prefer Delphi over .Net ?
Well, I am not Mark, but I would prefer Delphi over .Crap any time of the day. Though I am actually using FreePascal mostly these days, which is truly cross-platform compatible, in contrast to .NET which only pretends to be running on anything but Windows. So I am enjoying the benefits of a sane programming language without descending into dependency hell... ;P And as far as compiler warnings go, I tried them always with utmost respect, as almost always, they are at least a precursor for larger problems looming. In the rare exception that I deliberately chose to ignore a warning, this piece of code will properly be mark with some comment as to why, if there is no reasonable workaround to solve offending code.
-
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!!
"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
-
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!!
"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? :confused:
-
If you have a moment or two, could you please translate this into plain, proper English? :confused:
The English is plain enough. You just need to reorganize you thought processes to consider more options than simply being logical.
"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
-
Would you still prefer Delphi over .Net ?
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.
-
The English is plain enough. You just need to reorganize you thought processes to consider more options than simply being logical.
"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... ;P
-
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
:-\
-
Well, I am not Mark, but I would prefer Delphi over .Crap any time of the day. Though I am actually using FreePascal mostly these days, which is truly cross-platform compatible, in contrast to .NET which only pretends to be running on anything but Windows. So I am enjoying the benefits of a sane programming language without descending into dependency hell... ;P And as far as compiler warnings go, I tried them always with utmost respect, as almost always, they are at least a precursor for larger problems looming. In the rare exception that I deliberately chose to ignore a warning, this piece of code will properly be mark with some comment as to why, if there is no reasonable workaround to solve offending code.
For some reason your reply was marked as spam, probably by some Delphi hater, and I could not reply, but luckily an admin reverted that. Although I'm a .NET programmer I agree on the cross-platform thing, see: Slant pascal-based-languages-targeting-x86[^] Just saw a new entry in the list: CodeTyphon, so Pascal definitely is not dead and buried !
-
For some reason your reply was marked as spam, probably by some Delphi hater, and I could not reply, but luckily an admin reverted that. Although I'm a .NET programmer I agree on the cross-platform thing, see: Slant pascal-based-languages-targeting-x86[^] Just saw a new entry in the list: CodeTyphon, so Pascal definitely is not dead and buried !
Well, a lot of .NET fans can't handle the truth... ;P And Delphi is by far not the only Pascal based programming environment. I personally use FreePascal (Free Pascal - Advanced open source Pascal compiler for Pascal and Object Pascal - Home Page[^]) with the Lazarus IDE (Lazarus Homepage[^]) for years, is truly OpenSource on cross-platform on Windows, macOS and Linux, and then some... I had a look at CodeTyphon a few years ago, as someone was pushing it on a mailing list, but at least back then it wasn't quite ready "for prime time"...
