|
Oh, that's because it raining! The clouds are busy 
Skipper: We'll fix it.
Alex: Fix it? How you gonna fix this?
Skipper: Grit, spit and a whole lotta duct tape.
|
|
|
|
|
|
At $50 a month, I can buy a lot of bacon, not just the miserly 2 lbs offered. 
Will Rogers never met me.
|
|
|
|
|
For $50 (R570) I could eat bacon only two meals a day all month.
No object is so beautiful that, under certain conditions, it will not look ugly. - Oscar Wilde
|
|
|
|
|
You mean you don't already?
PooperPig - Coming Soon
|
|
|
|
|
I have only recently rejoined corporate employment and still eagerly await my first full salary next week. Then there will be bacon!
No object is so beautiful that, under certain conditions, it will not look ugly. - Oscar Wilde
|
|
|
|
|
At that price, I can eat bacon every meal for a month.
Will Rogers never met me.
|
|
|
|
|
I got an email today from Springer[^] telling me they have some holiday discount.
They have a $30 gift card. I decided to check it out and it seems you can get it from the site as well.
So I wanted to buy the book Agile! - The Good, the Hype and the Ugly[^] and of course I had to register. Upon registering I got another $5 discount.
I pay in euro's and I got a €30 discount. That means any book under €30 is free!
Unfortunately they didn't have anything I really liked, so I went for Agile! which is only €23,79 (yes, I wasted €6,21!  ).
Anyway, they have quite a lot of science books, so I thought the average CP'er might be interested in a $35/€30 discount.
Valid through december 31st.
And I guess Spinger got their free advertising. Thanks and you're welcome.
My blog[ ^]
public class SanderRossel : Lazy<Person>
{
public void DoWork()
{
throw new NotSupportedException();
}
}
|
|
|
|
|
Any link to where you can find those gift cards?
Wrong is evil and must be defeated. - Jeff Ello
(√-sh*t) 2
|
|
|
|
|
On the first fold of the Springer Shop page.
I wanna be a eunuchs developer! Pass me a bread knife!
|
|
|
|
|
That's odd, I couldn't see that on the tablet. But I can on the computer.
Wrong is evil and must be defeated. - Jeff Ello
(√-sh*t) 2
|
|
|
|
|
Maybe an error in the "mobile" version?
M.D.V. 
If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about?
Help me to understand what I'm saying, and I'll explain it better to you
Rating helpful answers is nice, but saying thanks can be even nicer.
|
|
|
|
|
Why are people so lazy? For example, how hard is it to
if (condition)
{
DoThis();
}
else
{
DoThat();
}
as opposed to:
if (condition)
DoThis();
else
DoThat();
Pedants 
|
|
|
|
|
They think they need to pay for each character entered?
According to my calculations, I should be able to retire about 5 years after I die.
|
|
|
|
|
I know what you're saying; however, there are times I find the second one easier to read.
For example, if I have several of those on a page the extra symbols spread stuff out.
I still do it the first way, but there are times when the second is easier for me to read.
|
|
|
|
|
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();
|
|
|
|
|
I prefer
if (something) DoAB(); for the latter. I never use it, but have recently come across it. It seems more readable to me.
No object is so beautiful that, under certain conditions, it will not look ugly. - Oscar Wilde
|
|
|
|
|
I don't do if() and the code in the same line. It is more a debug stuff. If I want to debug the if itself I put the breakpoint in that line. If I only want to debug the method call, after the if succeeded, I put the breakpoint in the call line.
|
|
|
|
|
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
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
