Java naming convention for boolean variable names: writerEnabled vs writerIsEnabled(布尔变量名称的 Java 命名约定:writerEnabled 与 writerIsEnabled)
问题描述
以下哪些声明符合 Java 的命名约定?
Which of the following declarations conforms to Java's naming conventions?
private boolean writerIsEnabled;
// with methods like
public boolean getWriterIsEnabled()
public void setWriterIsEnabled()
或
private boolean writerEnabled;
// with methods like
public boolean getWriterEnabled()
public void setWriterEnabled()
我个人认为名字writerIsEnabled"更具可读性,尤其是当您在这样的 if 语句中使用它时 -
I personally find the first name "writerIsEnabled" to be more readable, especially when you use it in an if statement like this -
if(writerIsEnabled)
{
//...
}
推荐答案
据我所知是这样的:
private boolean writerEnabled;
// with methods like
public boolean isWriterEnabled();
public void setWriterEnabled(boolean enabled);
无论类型是boolean还是Boolean,区别在于Getter以is开头,而不是get代码>.
Either when the type is boolean or Boolean, the difference is that the Getter starts with is instead of get.
我个人更喜欢 isWriterEnabled 方法.例如,像 JSF 这样的技术在访问属性时尊重该标准.EL 表达式用 is 和 get 确认.
Personally I prefer the isWriterEnabled approach. Technologies like, for example, JSF respect that standard when accessing properties. The EL expressions are acknowledged with is and get.
这篇关于布尔变量名称的 Java 命名约定:writerEnabled 与 writerIsEnabled的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持编程学习网!
本文标题为:布尔变量名称的 Java 命名约定:writerEnabled 与 writerIsEnabled
基础教程推荐
- 使用堆栈算法进行括号/括号匹配 2022-01-01
- RabbitMQ:消息保持“未确认"; 2022-01-01
- Spring AOP错误无法懒惰地为此建议构建thisJoinPoin 2022-09-13
- 问题http://apache.org/xml/features/xinclude测试日志4j 2 2022-01-01
- REST Web 服务返回 415 - 不支持的媒体类型 2022-01-01
- 无法复制:“比较方法违反了它的一般约定!" 2022-01-01
- 存储 20 位数字的数据类型 2022-01-01
- 如何对 Java Hashmap 中的值求和 2022-01-01
- 修改 void 函数的输入参数,然后读取 2022-01-01
- Struts2 URL 无法访问 2022-01-01
