|
*SOB* Hey! Our code works! *
* Or at least something almost similar if you disable the warnings.
I have lived with several Zen masters - all of them were cats.
His last invention was an evil Lasagna. It didn't kill anyone, and it actually tasted pretty good.
|
|
|
|
|
Order, order 
|
|
|
|
|
|
A classic !
|
|
|
|
|
Visual Studio: Quote: warning CS0168: The variable '_ex' is declared but never used
Everybody else: The F!
Me: ... So what, i need the Exception message!
Rules for the FOSW ![ ^]
if(!string.IsNullOrWhiteSpace(_signature))
{
MessageBox.Show("This is my signature: " + Environment.NewLine + _signature);
}
else
{
MessageBox.Show("404-Signature not found");
}
|
|
|
|
|
I used to go through the code and clean those out but then I decided life was too short.
When I did Delphi I would sometimes get a variable not initialized warning but when I initialized it I would get a value assigned but never used warning if the variable was in a try..except block.
|
|
|
|
|
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... 
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 !
|
|
|
|
|
|
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...
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
