为什么短路操作员不是默认操作员

Question

Given that a typical coding mantra is "Don't induce side effects in method calls." and that the only reason (that I know off - please enlighten me if I'm wrong) to not use short circuited operators is when you depend on the side effects of a method call in subsequent code. Why isn't the default operator in languages like C# and VB.NET not a short circuited version?

IE:

 if (Method1() & Method2()) {
 }

 if Method1 And Method2 then
 End if

 if (Method1() | Method2()) {
 }

 if Method1 Or Method2 then
 End if

Would actually (by default) mean

 if (Method1() && Method2()) {
 }

 if Method1 AndAlso Method2 then
 End if

 if (Method1() || Method2()) {
 }

 if Method1 OrElse Method2 then
 End if

Answer 1

Well there are two different reasons and two different answers I think.

For C# (and most Related older languages) the single ampersand or single pipe actually does bitwise operations against variables (bitwise as opposed to logical). That's why in all C/C++ code when someone wants a logical and you will see the double ampersand in their code.

For VB.NET I believe the answer is just history. Legacy Basic languages have always used "and" and "or" to do non-short circuit operations. It was an extremely poor decision but it's been carried all the way up to VB.NET.

It does bear mentioning that all the Basic languages utilize the "and/or" keywords to do bitwise operations as well. In older Basics there was no equivelant of the AndAlso or OrElse keywords to force short circuit so you had to nest If statements to get the logical equivelant of a short circuit and.