blocks|key|870040|text|我会修改选项1，使您使用的变量名称实际上有意义。也就是说，将"c2“的名称更改为类似于"stationIDIsEmpty”的名称(并将NOT移到条件中)。这样，条件是可读的，而不必来回浏览每个变量。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|870041|所以我的代码看起来可能是：|870042|boolean+enteredPassword+=+passwordField.getPassword().length+>+0;
boolean+stationIDIsEmpty+=+stationIDTextField.getText().trim().isEmpty();
boolean+userNameIsEmpty+=+userNameTextField.getText().trim().isEmpty();

if+(enteredPassword+&&+!stationIDIsEmpty+&&+!userNameIsEmpty)+{
+++okButton.setEnabled(true);
}|code-block|syntax|javascript|870043|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|L|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|M|8|@]|9|@]|A|$G|H]]|$1|I|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|J|$]]

I would modify option 1 so that you're using variable names that actually have a meaning. That is, change the name of "c2" to be something like "stationIDIsEmpty" (and move the NOT into the conditional). That way the conditional is readable without having to glance back and forth for every variable.

So my code would probably look like:

<pre><code>boolean enteredPassword = passwordField.getPassword().length &gt; 0;
boolean stationIDIsEmpty = stationIDTextField.getText().trim().isEmpty();
boolean userNameIsEmpty = userNameTextField.getText().trim().isEmpty();

if (enteredPassword &amp;&amp; !stationIDIsEmpty &amp;&amp; !userNameIsEmpty) {
 okButton.setEnabled(true);
}
</code></pre>

blocks|key|672757|text|if+(HasPassword()+&&+HasStation()+&&+HasUserName())
++okButton.setEnabled(true);


bool+HasPassword()+{
+return+passwordField.getPassword().length+>+0;
}|type|code-block|depth|inlineStyleRanges|entityRanges|data|syntax|javascript|672758|等。|unstyled|672759|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$B|C]]|$1|D|3|E|5|F|7|J|8|@]|9|@]|A|$]]|$1|G|3|-4|5|F|7|K|8|@]|9|@]|A|$]]]|H|$]]

<pre><code>if (HasPassword() &amp;&amp; HasStation() &amp;&amp; HasUserName())
 okButton.setEnabled(true);


bool HasPassword() {
 return passwordField.getPassword().length &gt; 0;
}
</code></pre>

etc.

blocks|key|870066|text|就我个人而言，我喜欢第二种方式，因为我发现使用这种方法可以使条件词的预测变得清晰。也就是说，如果这个方法做得很好，你就可以通过"verablizing“来理解条件(不管你是否真的说它是无关紧要的)。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|870067|也就是说，使用第二个选项，可以清楚地看到，条件大致上是这样翻译的：“如果密码长度大于零，且stationIDTextField+(修整)不是空的，而usernameTextField+(修整)不是空的，那么.”|870068|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

Personally, I like the second way, because I find that using that way can make the predication of the conditionals clear. That is, with that method done properly, you can make the conditional comprehensible by "verablizing" it (whether or not you actually speak it is irrelevant).

That is, with your second option, it becomes clear that your conditional translates roughly as this: "If the password length is greater than zero, AND the stationIDTextField (trimmed) is NOT empty, AND the usernameTextField (trimmed) is NOT empty, then..."

blocks|key|870081|text|我更喜欢以下几点：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|870082|if+(passwordField.getPassword().length+>+0
++++&&+!+stationIDTextField.getText().trim().isEmpty()
++++&&+!+userNameTextField.getText().trim().isEmpty())
{
++++okButton.setEnabled(true);
}|code-block|syntax|javascript|870083|通过这种编码风格，我完成了两件事：|870084|我可以很容易地看到，if的每一行额外的行都是条件的一部分，因为在乞讨时，会出现&&+(或\\)。|unordered-list-item|870085|我可以很容易地看到if语句的结尾位置，因为在下一行有{。|870086|entityMap^0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|P|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|Q|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|R|8|@]|9|@]|A|$]]|$1|I|3|J|5|K|7|S|8|@]|9|@]|A|$]]|$1|L|3|M|5|K|7|T|8|@]|9|@]|A|$]]|$1|N|3|-4|5|6|7|U|8|@]|9|@]|A|$]]]|O|$]]

I prefer the following:

<pre><code>if (passwordField.getPassword().length &gt; 0
 &amp;&amp; ! stationIDTextField.getText().trim().isEmpty()
 &amp;&amp; ! userNameTextField.getText().trim().isEmpty())
{
 okButton.setEnabled(true);
}
</code></pre>

With this coding style I accomplish two things:

<ul>
<li>I can easily see that each extra line of the if is part of the condition because of the &amp;&amp; (or ||) at the beggining.</li>
<li>I can easily see where the if statement ends because of the { at the next line.</li>
</ul>

blocks|key|870112|text|Option1是应用重构'用查询替换temp‘的主要工具。原因是有人可以在变量之间填充代码，并检查和更改代码的行为。或者检查可能是用陈旧的值进行的。在初始化和检查之间对文本字段进行了更新。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|870113|所以我的尝试是|870114|if+(GetPasswordLength()+>+0+
+++&&+FieldHelper.IsNotEmpty(stationIDTextField)+
+++&&+FieldHelper.IsNotEmpty(userNameTextField)+
{
+++okButton.setEnabled(true);
}|code-block|syntax|javascript|870115|FieldHelper是一个具有公共静态方法的类(在C#中也称为实用程序类/静态类)|870116|entityMap|0|LINK|mutability|MUTABLE|url|http://www.refactoring.com/catalog/replaceTempWithQuery.html^0|D|9|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|U|8|@]|9|@$A|V|B|W|1|X]]|C|$]]|$1|D|3|E|5|6|7|Y|8|@]|9|@]|C|$]]|$1|F|3|G|5|H|7|Z|8|@]|9|@]|C|$I|J]]|$1|K|3|L|5|6|7|10|8|@]|9|@]|C|$]]|$1|M|3|-4|5|6|7|11|8|@]|9|@]|C|$]]]|N|$O|$5|P|Q|R|C|$S|T]]]]

Option1 is prime for applying the refactoring '<a href="http://www.refactoring.com/catalog/replaceTempWithQuery.html" rel="nofollow noreferrer">Replace temp with Query</a>'. The reason being that someone can stuff in code between the variable is initialized and the check and change the behavior of the code. Or the check might be made with stale values.. an update has been made to the textfields between initialization and checking.

So my attempt at this would be

<pre><code>if (GetPasswordLength() &gt; 0 
 &amp;&amp; FieldHelper.IsNotEmpty(stationIDTextField) 
 &amp;&amp; FieldHelper.IsNotEmpty(userNameTextField) 
{
 okButton.setEnabled(true);
}
</code></pre>

FieldHelper is a class with public static methods (also called a Utility class / Static class in C#)

blocks|key|2202215|text|注意，选项1不允许短路行为。也就是说，在计算第一个条件的结果之前，计算所有条件项的值。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2202216|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

Note that option 1 does not allow for short circuiting behavior. That is, you calculate the value of all of the conditionals before evaluating the result of the first.

blocks|key|870130|text|我投了克里斯·布兰德斯玛的票。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|870131|但我只想提一下选项1的主要问题，那就是您正在失去&&的好处。使用选项一，虽然我认为它更易读，但您正在处理可能不需要的比较。|870132|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

I voted for Chris Brandsma's answer.

But just wanted to mention the main issue I have with Option 1 is you are losing the benefit of &amp;&amp;. With option one, although I think it's more readable, you are processing comparisons when they may not be required.

What would be the most readable/best way to write a multiple conditional check such as shown below?

Two possibilities that I could think of (this is Java but the language really doesn't matter here):

Option 1:

<pre><code> boolean c1 = passwordField.getPassword().length &gt; 0;
 boolean c2 = !stationIDTextField.getText().trim().isEmpty();
 boolean c3 = !userNameTextField.getText().trim().isEmpty();

 if (c1 &amp;&amp; c2 &amp;&amp; c3) {
 okButton.setEnabled(true);
 }
</code></pre>

Option 2:

<pre><code> if (passwordField.getPassword().length &gt; 0 &amp;&amp;
 !stationIDTextField.getText().trim().isEmpty() &amp;&amp;
 !userNameTextField.getText().trim().isEmpty() {
 okButton.setEnabled(true);
 }
</code></pre>

What I don't like about option 2 is that the line wraps and then indentation becomes a pain. What I don't like about option 1 is that it creates variables for nothing and requires looking at two places.

So what do you think? Any other options?

Most readable way to write simple conditional check

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

编写多个条件检查的最易读/最好的方法是什么，如下面所示？我可以想到两种可能性(这是Java，但语言在这里并不重要)：选项1:   boolean c1 = passwordField.getPassword().length > 0;   boolean c2 = !stationIDTextField.getText...

问最易读的编写简单条件检查的方法
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问最易读的编写简单条件检查的方法EN