|
This is true. I always use separate lines for everything myself, but all I was saying is I find if (if stuff) [then stuff]; on one line more readable, in established and (hopefully) debugged code. If I have to debug it myself, I just hit enter and add a breakpoint on the new line. Then use the "source control undo" in solution explorer to revert back to the prior pristine state.
No object is so beautiful that, under certain conditions, it will not look ugly. - Oscar Wilde
|
|
|
|
|
I understand... and I can't say I disagree... that arrives to the point of preference, not to the point of usefulness.
But one thing I never do is 2 (or more) real calls in the same line:
SomeObject.DoCallOne().DoCall2(otherObject.AnotherCallWithAResult(), evenAnotherObject.WithEvenAnExtraCall(), theFinal.ObjectWithTheFinalCall());
modified 11-Dec-14 13:27pm.
|
|
|
|
|
Just your contrived example hurts my eyes. I'd hate to see that in real life. 
No object is so beautiful that, under certain conditions, it will not look ugly. - Oscar Wilde
|
|
|
|
|
Here's a Visual Studio trick:
To debug the if, make sure the text cursor is somewhere in the if condition and press F9.
To debug the method call after the if succeeded, make sure the text cursor is somewhere in the method call and press F9.
Happy Debugging 
|
|
|
|
|
Imagine the if and the call are in the same line. Yet, the condition is false 99% of the time.
Also, the method being called is called from many other places.
If things are in two lines, simply put the breakpoint inside the if, not on the if line. If it is in the same line, you can't do that. Putting the breakpoint inside the method call will not help either, as it is called from many other places, so the best you can do is to create a conditional breakpoint.
I prefer to have things in two lines and put the breakpoint exactly where it is needed.
|
|
|
|
|
|
Cool, thanks. I've bookmarked those.
No object is so beautiful that, under certain conditions, it will not look ugly. - Oscar Wilde
|
|
|
|
|
Brady Kelly wrote: I prefer
if (something) DoAB(); for the latter. I never use it, but have recently come across it. It seems more readable to me.
Me too, if you must omit the braces then it's best to put it on one line. That way you don't have to worry about someone coming along later, not paying attention, and doing this:
if (something)
DoA();
DoB();
|
|
|
|
|
That works fine until you get this in the code after all 
if ((err = SSLHashSHA1.update(&hashCtx, &serverRandom)) != 0)
goto fail;
if ((err = SSLHashSHA1.update(&hashCtx, &signedParams)) != 0)
goto fail;
goto fail;
if ((err = SSLHashSHA1.final(&hashCtx, &hashOut)) != 0)
goto fail;
When I first saw that bug I got even more convinced see that my approach to braces everywhere as a must works better in the end.
Banking establishments are more dangerous than standing armies. T.Jefferson
|
|
|
|
|
I, for example, would never write the code like that. I can write an if without the {}, but I always put an extra line break after the call. And seeing two lines after the if simply looks wrong.
if ((err = SSLHashSHA1.update(&hashCtx, &serverRandom)) != 0)
goto fail;
if ((err = SSLHashSHA1.update(&hashCtx, &signedParams)) != 0)
goto fail;
goto fail;
if ((err = SSLHashSHA1.final(&hashCtx, &hashOut)) != 0)
goto fail;
So, this kind of error is as ugly to me as this (in fact, even uglier as the excessive {} somewhat hide the problem):
if ((err = SSLHashSHA1.update(&hashCtx, &serverRandom)) != 0)
{
goto fail;
}
if ((err = SSLHashSHA1.update(&hashCtx, &signedParams)) != 0)
{
goto fail;
}
goto fail;
if ((err = SSLHashSHA1.final(&hashCtx, &hashOut)) != 0)
{
goto fail;
}
But developers can also commit these errors (and by simply taking a looks without reading the code, I don't spot anything wrong):
if ((err = SSLHashSHA1.update(&hashCtx, &serverRandom)) != 0)
{
goto fail;
}
if ((err = SSLHashSHA1.update(&hashCtx, &signedParams)) != 0)
{
goto fail;
}
{
goto fail;
}
if ((err = SSLHashSHA1.final(&hashCtx, &hashOut)) != 0)
{
goto fail;
}
if ((err = SSLHashSHA1.update(&hashCtx, &serverRandom)) != 0)
{
goto fail;
}
if ((err = SSLHashSHA1.update(&hashCtx, &signedParams)) != 0)
{
goto fail;
}
else
{
goto fail;
}
if ((err = SSLHashSHA1.final(&hashCtx, &hashOut)) != 0)
{
goto fail;
}
modified 11-Dec-14 13:35pm.
|
|
|
|
|
Well, I won't write anything such as that either. But since this a real world example of infamous 'goto fail' bug obviously other people do.
In general I'd say that none of your samples with braces would've passed my code review, but I admit your first sample should attract review attention as well, it'll probably will attract enough attention from any reviewer. Still I'd say that with braces style the code like that most probably would not leave the developer and will be fixed before review
Banking establishments are more dangerous than standing armies. T.Jefferson
|
|
|
|
|
I don't care what way you do it as long as it is not:
if (something) {
DoA()
}
Yuck!
But seriously - if the biggest problem your project has is where people put or don't put the braces you are doing pretty good.
|
|
|
|
|
Paulo Zemek wrote:
I agree with you. And I am actually the kind of person that when has to modify something like:
if (something)
{
DoA();
DoB();
}
To only call a DoAB(), I will go there and kill the extra { and }. So, I have more work doing that, but I keep consistency.
So, it becomes:
if (something)
DoAB(); |
Are you serious? You re-factor and combine methods just so you can avoid braces and use a dangerous bad practice?
|
|
|
|
|
No, I don't refactor and combine methods... I was only giving an example. What's more probably is that I extract an entire block (with many calls) into a single method. But for the example I used two calls.
|
|
|
|
|
And why couldn't you write
if (condition)
{
this.DoThis();
}
else
{
this.DoThat();
}Now this code is totally unambiguous
Although I know some people who really hate this...
My blog[ ^]
public class SanderRossel : Lazy<Person>
{
public void DoWork()
{
throw new NotSupportedException();
}
}
|
|
|
|
|
That's not good enough...
if
(
condition
)
{
this
.
DoThis
(
)
;
}
else
{
this
.
DoThat
(
)
;
}
It's not properly formatted until there's only one token per line.
|
|
|
|
|
Oooooooo, look at how easy that is to maintain now!! :drool:
Jeremy Falcon
|
|
|
|
|
if (condition) { this.DoThis(); } else { this.DoThat(); }
You probably meant
Ian Shlasko wrote: It's not properly formatted until there's only one token per line in the entire application.
I guess it's theoretically possible... 
My blog[ ^]
public class SanderRossel : Lazy<Person>
{
public void DoWork()
{
throw new NotSupportedException();
}
}
|
|
|
|
|
Way back in my College days the Software Lecturer told us (the class) it wasn't possible to do the above. I proved her wrong by writing a short Pascal (I think) program with no returns all on one line, ah Youth 
|
|
|
|
|
The end of the story -
"...and that's how I got to repeat introduction to programming!!"
|
|
|
|
|
Quite. The maturity of a programming language may (in part) be calculated by how many newlines are required. A proper language requires none.
|
|
|
|
|
PIEBALDconsult wrote: Quite. The maturity of a programming language may (in part) be calculated by how many newlines are required. A proper language requires none.
Just for making that statement, you should be forced to a maintain decade-old Perl CGI system.
|
|
|
|
|
Perl is a scripting language; not a programming language.
|
|
|
|
|
Yeah true, you really need to be pedantic about a joke?
|
|
|
|
|
No, but I really need to be demeaning of Perl. 
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
