Why would it become a problem?jake benn wrote:Why doesn't the compiler put the kibosh on that before it becomes a problem?
Why not when its behavior is specified.jake benn wrote:What is the point of allowing that statement?
No. Null is not false. It are 2 completely different things. This does not compile:jake benn wrote:Doesn't an empty boolean equal null and isn't null false and thereby allowing this statement to fall through?
No difference.jake benn wrote:What is the difference between that and this?
"Any fool can write code that a computer can understand. Good programmers write code that humans can understand." --- Martin Fowler
Please correct my English.
SCJA
When I die, I want people to look at me and say "Yeah, he might have been crazy, but that was one zarkin frood that knew where his towel was."
SCJA
When I die, I want people to look at me and say "Yeah, he might have been crazy, but that was one zarkin frood that knew where his towel was."
"Any fool can write code that a computer can understand. Good programmers write code that humans can understand." --- Martin Fowler
Please correct my English.
"Any fool can write code that a computer can understand. Good programmers write code that humans can understand." --- Martin Fowler
Please correct my English.
SCJA
When I die, I want people to look at me and say "Yeah, he might have been crazy, but that was one zarkin frood that knew where his towel was."
With a little knowledge, a cast iron skillet is non-stick and lasts a lifetime. |