C# bool 表达式求值顺序
可能的重复：
== 运算符和操作数
好吧，这可能是个愚蠢的问题，但是在谷歌中搜索（似乎不能实际上搜索精确的短语，即使带引号）
之间存在任何差异怎么办？
如果 if(false ==
和
if(
C# 中？我熟悉 C# 的表达式求值，并且了解如果您执行以下操作，顺序将如何有意义：
if(AccountIsInvalid || AccountIsUnregistered)
我不需要大量课程，但想了解原因有些人更喜欢使用 false==.... 路线做事。
Possible Duplicate:
== Operator and operandsPossible Duplicates:
Is there any difference between if(a==5) or if(5==a) in C#?
== Operator and operands
Ok, this may be stupid question, but searching in google (cant seem to ACTUALLY search for an exact phrase even with quotes)
What if any difference is there between
if(false == <somecondition>){
and
if(<somecondition> == false){
in C#? I am familiar with c#'s expression evalution, and understand how the order would make sense if you were doing something like:
if(AccountIsInvalid || AccountIsUnregistered)
I dont need a huge lesson, but would like to understand why some people prefer to do things with false==.... route.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（4）
就我个人而言，我从不将任何东西与虚假或真实进行比较。
我会选择：
或：
Personally, I never compare anything to false or true.
I would go with:
or:
在 C 中，也许有一些理由这样做，因为你很容易犯错误并使用赋值运算符而不是比较运算符，但在 C# 中它不应该有任何区别 - 你将得到一个编译如果您使用赋值运算符，则会发出警告。如果赋值是不同的类型（例如 int），则会导致错误，因为结果不是 if 语句的合法表达式。
我更希望它是
真实的，而不是与错误（或真实的）进行比较。
In C there would have been, perhaps, some reason to do this as you could easily make a mistake and use the assignment operator instead of the comparison operator, but in C# it shouldn't make any difference -- you'll get a compile warning if you use the assignment operator. If the assignment were a different type (say int), it would result in an error, since the result wouldn't be a legal expression for the if statement.
I would prefer it to be
rather than a comparison to false (or true, for that matter).
在执行任何优化或短路之前，编译器需要将
true或false值，因此没有理由为什么编译器会计算表达式; == false false ==任何不同。这肯定是一个风格问题，而且只是风格问题。
Before performing any optimizations or short-circuits, the compiler needs to resolve
<somecondition>totrueorfalsevalue, thus there is no reason why the compiler would evaluate the expressions<somecondition> == falseandfalse == <somecondition>any differently.This must surely be an issue of style, and style only.
这在 C# 中并不重要，就像在 c/c++ 中一样，因为条件必须计算为布尔值。
This doesn't matter in C# like it does in c/c++ because conditions must evaluate to a boolean.