Since when does m$ use winzip selfextractor anyway?
Having a goto can be a good thing, allthough it should be avoided at all cost. Recommending goto is a bad thing. It leads to spaghetti programming. I agree that there should be another way to break out of nested loops!
if (i=0) isn't always a typo. You could be testing if the assignment succeeded correctly. A compiler should not complain about this imho. Consider int i = 5; if (i) {... } The compiler would complain because 5 is not a bool value. Do you like such behaviour?
In C#, the example int i =...; F(i); if (i = 0)// Bug: the test should be (i == 0) G(); is invalid because the expression i = 0 is of type int, and if statements require an expression of type bool.
So you can't assign a variable in an if statement?
So true is no longer Everything but nothing(null, 0, empty)?
Since when does m$ use winzip selfextractor anyway?
Having a goto can be a good thing, allthough it should be avoided at all cost.
Recommending goto is a bad thing. It leads to spaghetti programming.
I agree that there should be another way to break out of nested loops!
if (i=0) isn't always a typo. You could be testing if the assignment succeeded correctly. ... }
A compiler should not complain about this imho.
Consider
int i = 5;
if (i) {
The compiler would complain because 5 is not a bool value. Do you like such behaviour?
So you can't assign a variable in an if statement?
So true is no longer Everything but nothing(null, 0, empty)?
I want if(expression), not if(bool)!!