In Java 3 = 12
virtualspecies.com
In Java 3 = 12
1–10 of 55 posts
Re: In Java 3 = 12
#21) Left-associativity
2) The price you pay for type coercion. Be thankful Java defines the order of evaluation. Not all languages which coerce specify the order of evaluation.
Re: In Java 3 = 12
#3And in php (after https://eev.ee/blog/2012/04/09/php-a-fractal-of-bad-design/):
"foo" == TRUE and "foo" == 0 but TRUE != 0
123 == "123foo" but "123" != "123foo"
"6" == " 6", "4.2" == "4.20" and "133" == "0133", but 133 != 0133, "0x10" == "16" and "1e3" == "1000"
Re: In Java 3 = 12
#4This was touched literally on second exercises (so second hour of learning Java) on university when I learned Java.
Re: In Java 3 = 12
#51) Left-associativity 2) The price you pay for type coercion. Be thankful Java defines the order of evaluation. Not all languages which coerce specify the order of evaluation.
I'm glad some of the newer languages like rust and go just dump implicit coersion altogether. Yeah it's convenient but it's not worth the headache and subtle bugs.
Re: In Java 3 = 12
#6And in php (after https://eev.ee/blog/2012/04/09/php-a-fractal-of-bad-design/ ): "foo" == TRUE and "foo" == 0 but TRUE != 0 123 == "123foo" but "123" != "123foo" "6" == " 6", "4.2" == "4.20" and "133" == "0133", but 133 != 0133, "0x10" == "16" and "1e3" == "1000"
[deleted]
Re: In Java 3 = 12
#7Does the same in .NET
https://dotnetfiddle.net/0vkSCV
Used .NET for 15 years and never knew this...
Re: In Java 3 = 12
#81) Left-associativity 2) The price you pay for type coercion. Be thankful Java defines the order of evaluation. Not all languages which coerce specify the order of evaluation.
Yes but that's strange. Java is such a staticaly typed language you would not expect it to do that if you are like me and don't know it very well.
While Python is very dynamic, but:
>>> print(1 + 2 + "=" + 1 + 2)
Traceback (most recent call last):
File "", line 1, in
TypeError: unsupported operand type(s) for +: 'int' and 'str'Re: In Java 3 = 12
#91) Left-associativity 2) The price you pay for type coercion. Be thankful Java defines the order of evaluation. Not all languages which coerce specify the order of evaluation.
Yes but that's strange. Java is such a staticaly typed language you would not expect it to do that if you are like me and don't know it very well. While Python is very dynamic, but: >>> print(1 + 2 + "=" + 1 + 2) Traceback (most recent call last): File " ", line 1, in TypeError: unsupported operand type(s) for +: 'int' and 'str'
dynamic vs. static typing is independent of strong vs. weak typing. strong typing is basically allowing fewer implicit converstations, weak more. static means type checking happens before runtime, dynamic means the opposite.
Re: In Java 3 = 12
#101) Left-associativity 2) The price you pay for type coercion. Be thankful Java defines the order of evaluation. Not all languages which coerce specify the order of evaluation.
Yes but that's strange. Java is such a staticaly typed language you would not expect it to do that if you are like me and don't know it very well. While Python is very dynamic, but: >>> print(1 + 2 + "=" + 1 + 2) Traceback (most recent call last): File " ", line 1, in TypeError: unsupported operand type(s) for +: 'int' and 'str'
that's also strange to me.
you are seeing this error because python is strong typing language.
but this is weird that java is also strong typing language[0]
0: https://en.m.wikipedia.org/wiki/Java_(programming_language)