|
Well said!
Software Zen: delete this;
|
|
|
|
|
Tax the little people. They'll thank you for it.
What scum.
|
|
|
|
|
When working from home I'm already paying for extra electricity, water... I'm also less pollute the air - no commute...
So already payed for the 'pleasure' of working from home...
"The only place where Success comes before Work is in the dictionary." Vidal Sassoon, 1928 - 2012
|
|
|
|
|
A handful of commands was all it took for untrusted users to become all-powerful. "sudo make me a sandwich"
|
|
|
|
|
I realised there's a clear rationale behind my aversion to else statements though. I believe that they shouldn't be used, and should be treated as a code smell instead. Or what?
|
|
|
|
|
Kent Sharkey wrote: Or what?
goto Hell.
|
|
|
|
|
OK, I'm going to have to create a bunch of burner accounts just to upvote this more
TTFN - Kent
|
|
|
|
|
I'm glad somebody appreciates my sardonic humor.
|
|
|
|
|
You also made me laugh!
|
|
|
|
|
It's actually a decent article, though I wouldn't get overly religious about its prescription.
Why not take it a step further and say that if is a code smell? A senior developer held that opinion 40 years ago, saying that if means you don't know what you're doing. Some of today's terminology didn't exist then, but in modern parlance I think he meant that many if statements--more so those with an else clause, and especially switch statements--should be replaced by calling a virtual function. This is certainly true when polymorphic behavior applies, which we implemented manually by putting function pointers into a struct selected by a type index:
polymorphs[type_id].function(arguments);
|
|
|
|
|
So his primary method of removing "else" is to have multiple return points.
Talk about code smell.
|
|
|
|
|
I don't object to multiple return points, certainly not from outer-level statements.
I once refactored code written by a zealot who must have grown up with Pascal and so believed that you could/should only return at the end of a function. Various functions would set a skip bool that was checked by every ensuing control statement or code block, just to see whether it should be skipped to eventually get to the end of the function. Utter dross.
modified 11-Nov-20 15:01pm.
|
|
|
|
|
You should have put a governor on his car and set it for 15mph.
|
|
|
|
|
Beyond my technical ability. But I've heard told that a potato in the exhaust works just as effectively.
|
|
|
|
|
|
|
It was still good for some laughs in Beverly Hills Cop.
|
|
|
|
|
i've worked places where that is the official (and unofficial) style for some languages.
return immediately for errors, don't if around them; don't nest ifs.
|
|
|
|
|
Write better code and don't litter your functions with return statements
|
|
|
|
|
I "love" articles which preach writing more readable code and then illustrate it with extremely unreadable code which is hard to debug.
|
|
|
|
|
You will be a better programmer when you understand that there is no a 'one-tool-for-all' solution for all problems... And no else here...
"The only place where Success comes before Work is in the dictionary." Vidal Sassoon, 1928 - 2012
|
|
|
|
|
Ah, "Else considered harmful". I admit I haven't seen that one yet
|
|
|
|
|
Back in May I blogged about the C# 9.0 plans, and the following is an updated version of that post to match what we actually ended up shipping. "Number nine, number nine, number nine..."
However did I manage to not include this one yesterday?
|
|
|
|
|
Wireless network in Kenya to use light beams, like fiber but without the cables. It's all fun-and-games until someone comes with a mirror
|
|
|
|
|
Kent Sharkey wrote: It's all fun-and-games until someone comes with a mirror
We can flock to the party until someone rains on our parade.
|
|
|
|