The Lounge is rated PG. If you're about to post something you wouldn't want your
kid sister to read then don't post it. No flame wars, no abusive conduct, no programming
questions and please don't post ads.
I'm working on a code base which has *lots* of misspellings. Someone wrote a method by this name: StartInspectionDawnload() My question: Is that something that should only happen each morning? And at a different time each day?
As [almost] a real question: Why do so many people leave code in place that has something spelled wrong?
If you have a deprecation policy in place eventually (eg the major version after the one where it's deprecated) you can change the annotation from false to true and convert it from a compile time warning to an error.
Did you ever see history portrayed as an old man with a wise brow and pulseless heart, waging all things in the balance of reason?
Is not rather the genius of history like an eternal, imploring maiden, full of fire, with a burning heart and flaming soul, humanly warm and humanly beautiful?
Training a telescope on one’s own belly button will only reveal lint. You like that? You go right on staring at it. I prefer looking at galaxies.
-- Sarah Hoyt
Once it gets in, if it's used by other sources not under your control, you're doomed to leave it in in some form or another - at the very least adding the corrected one, redirecting the misspelled one to the correct one and deprecating the former.
The real question is: how come nobody checks anything before releasing? At least the interface functions should be checked and documented before release so have the time to make the necessary changes.
Is this a snippet from Nitin Sawant's code? If so, that might go a long way towards explaining why his co-workers hate him.
".45 ACP - because shooting twice is just silly" - JSOP, 2010 - You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010 - When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013
On a related note, the system I work on has a couple of million data collection points. Sometimes there are spelling errors in the point names; while it may seem prudent to correct them, if those points are used in calculations, that causes the calculation to fail... but only when the calculation engine is restarted. Otherwise, the calculation engine parses the input names at load time and then uses the internal point reference number - something that never changes.
Some of the layered products (displays, etc.) use the collection point name, but, the newer products are maintaining the internal point reference number and, when a point is renamed, the change is made auto-magically in the newer products.
I think it's intensional, done just for the simple joy of watching people with OCD go nuts.
"the debugger doesn't tell me anything because this code compiles just fine" - random QA comment "Facebook is where you tell lies to your friends. Twitter is where you tell the truth to strangers." - chriselst "I don't drink any more... then again, I don't drink any less." - Mike Mullikins uncle
Sounds like a Southerner (from the US South) wrote that method because it's spelled like they talk.
#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