The Lounge is rated Safe For Work. If you're about to post something inappropriate for a shared office environment, then don't post it. No ads, no abuse, and no programming questions. Trolling, (political, climate, religious or whatever) will result in your account being removed.
My default project is edited to include "Treat warnings as errors: All" and "Warning level: 4", as well as ticking "XML documentation file" - which gives a error if I forget the XML header for a public item.
If your code has warnings, there is probably something you haven't thought of ... particularly if you are a beginner.
Sent from my Amstrad PC 1640 Never throw anything away, Griff
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
AntiTwitter: @DalekDave is now a follower!
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.
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[^]
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
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.
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