|
And, in many installations it would remain the way it is. In order to change code thee must be a request for an enhancement or to fix a problem. If you fix something that's 'working' and introduce a new bug you can be for the high-jump.
Paul
|
|
|
|
|
It probably depends on where you work and if you're the one who has to support the code in the future. If I was the one who had the support the code, I'd change it. At least then if something breaks, I'm also the one who has to fix it.
|
|
|
|
|
If it was my code, my responsibility etc, so would I. I have worked as a contractor for 25 years, and I can assure you it would NOT be changed at many places where I have worked without an RFC (request for change), cost benefit analysis, documentation, code review, test plan, version control, comment out old code and insert new, etc etc.
However, if you are changing a part of the system which incorporates that particular bit of code then kill it, cus you have to do all of the above anyway.
However, sometimes code you think does nothing, may do something. A slight change to the above algorithm, say that it becomes possible to drop through the code and exit without returning a return value. This throws an exception that is caught elsewhere. (That, for example, would happen with Powerbuilder 8+).
Also, there may be a difference in behaviour between just returning true and looking at a passed invalid parameter (say a null pointer).
For these sort of reasons, many sites will use an "if it ain't broke then don't fix it" approach. Chaning code withour permission is loose-cannon behaviour. I am not trying to support this position, all the fibres of my soul want to change code when I see it is badly written, designed or implemented. You just have to learn to sit on your coding hands.
Paul
|
|
|
|
|
Wow, I must say I am still learning the ways of software development but your post is interesting and enlightening in so many ways. Very interesting to try and understand all the ramifications of changing even the smallest and seemingly insignificant piece of code in an already developed project. I suppose to most sobering fact is that there are probably many cases where you just have to put up with bad code purely due to the fact that it is just not cost effective to go and correct the mistake/s.
|
|
|
|
|
Your point is well taken. I can see where a change to this code as innocent as it sounds could cause a large problem for everyone. This without doubt explains why software created by the giants frequently breaks. The Coders don't want to go through the mountain of $xxt and paperwork it would take to fix a seemingly minor problem. And so we go back to a time when we put in NOPs into ASM code to later take it out and call it an update.
|
|
|
|
|
yeah, but its a function that returns true no mater what the conditions are, and judging by the calls it makes, doesnt do anything else.so..
|
|
|
|
|
There could be some side effect of the GetValueAsLong() method call that the rest of the system is depending on. If the code looks bad at face value, you should only assume it gets worse as you dig into it.
|
|
|
|
|
-irregardless- 
That's a good one for this discussion. I bet if you changed that to simply return true all the time, it would totally break the application...
|
|
|
|
|
Ihave seen much strangers things happen!
INTP
"Program testing can be used to show the presence of bugs, but never to show their absence."Edsger Dijkstra
|
|
|
|
|
I can see you have been in the industry a while - I agree. I can think of at least 4 reasons why the code above may behave differently to "return true", depending on the language and hardware.
Paul
|
|
|
|
|
I'm wondering if the function that returns a 'long', actually does some kind of work behind the scenes. It's not good style, but it's not unheard of. It's a good one for The Daily WTF (I reject the new name of that site)
And yeah I've been around a while... took a few years off to get a Biology degree, but it didn't do me much good. I went right back into this industry, but I found it much easier to get a job after college.
|
|
|
|
|
Jasmine2501 wrote: I'm wondering if the function that returns a 'long', actually does some kind of work behind the scenes.
And this function is then called once or twice?
And expected to not have side effects?
If that is the case, someone needs a serious spanking (maybe me )
You simply do not code that way.
And newbies have the right to be educated properly! Thats their supervisors responsibilities!
Failure is not an option - it's built right in.
|
|
|
|
|
Yeah not good. I always look at the code my guys are doing. In a job ad we recently advertised that you can learn on the job with an experienced mentor. We still didn't find anybody 
|
|
|
|
|
irrespective or regardless? unless you really did mean irregardless, but then I'm really confused.
The pleasure's been all mine...and in the end, that's all that's really important.
|
|
|
|
|
this is 'cause it is necessary document methods with the name of the author, so will be always possible to give to the author 100 lashs ...i'm joking.....1000 lashs ))
|
|
|
|
|
Placeholder where they never put the live code in?
|
|
|
|
|
to_be_defined wrote: Every time I read this I get an overwhelming feeling of wonder...
All sales types are valid because the customer is always right. 
_________________________
Asu no koto o ieba, tenjo de nezumi ga warau.
Talk about things of tomorrow and the mice in the ceiling laugh. (Japanese Proverb)
|
|
|
|
|
Slick. Now if I could only hack into my girlfriend's brain and override her IsHorny function with this algo, life would be good.
|
|
|
|
|
As a predendum to my Cobol message I regret the passing of limited-length variable names. In IBM assembler it used to be 8 characters. I was updating some communication software, and it wasn't until I sorted out the variable names that the code began to make sense. Here are some of the variable names I remember and their meaning:
yek - return key
ecaps - backspace
antelope - Line feed
turfd - shift
unyon - carat
Sadly, I cannot remember many more...
Paul
|
|
|
|
|
I wonder what "sentence" they built from these names
|
|
|
|
|
Ah the memories, those were the good old days.
Haven't programmed assembly in many years (8086 - 80386) but used to be language of choice.
Thanks for the memories
Mike
Theres light at the end of the tunnel. Lord I hope it ain't no train!
|
|
|
|
|
Ret Orrick wrote: Sadly, I cannot remember many more...
I'm amazed you could remember those. 
I remember in one assembler program, we had a PREG (basically, a record structure definition) that was being used during a batch update process. The original dev called it BTCHPREG. 
BW
Quick to judge, quick to anger, slow to understand.
Ignorance and prejudice and fear walk hand in hand.
-- Neil Peart
|
|
|
|
|
obviously management was too intimidated by assembly to participate in code reviews of any sort.
--
CleaKO The sad part about this instance is that none of the users ever said anything [about the problem].
Pete O`Hanlon Doesn't that just tell you everything you need to know about users?
|
|
|
|
|
Some of my earliest serious work was done in F77 on a PDP-11 running RSX-11 and it had the name length limit. It wasn't that big of an issue then as I recall. Shortly thereafter we moved to VAXes and its dialect of FORTRAN had no name length limits.
These days, every time I see assembly language I am reminded why high level languages were invented.
|
|
|
|
|
The shortest most annoying program on a PDP-8 (entered with the switches) was...
Ring bell
Branch to start
Paul
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
![Badger | [badger,badger,badger,badger...]](https://www.codeproject.com/script/Forums/Images/badger.gif)
