Oops, I was wrong, besides the operator/expression resolution priority
you pointed out. In the spec 14.2.3, case of lack of "single best
operator" a compile time error should occur. I only read 14.6.1 and
thought that they are just predefined ones.
I'll file it to bugzilla. Thanks.
Atsushi Eno
On 6/19/05, Atsushi Eno <[EMAIL PROTECTED]> wrote:
> I think this is the expected behavior. What that code actually does is:
>
> Console.WriteLine (
> cad1.Equals(cad2) + ",", // first argument
> + cad2.Equals(cad3) + "," + cad1.Equals(cad3)); // second argument
>
> The second + is interp
Hello,
I think this is the expected behavior. What that code actually does is:
Console.WriteLine (
cad1.Equals(cad2) + ",", // first argument
+ cad2.Equals(cad3) + "," + cad1.Equals(cad3)); // second argument
The second + is interpreted as an unary operator and thus it is correct
behavio
Hello!
Look for the comma ',' inserted in the code I append
(just next "cad1.Equals(cad2) +" in the seventh line).
I think it should be a parser error, shouldn't be? But the compiler
doesn't complain at all. The result with the comma is:
False,
and without the comma
False,False,True
I have pro
