blocks|key|1248126|text|四个空格--这是上帝的用处。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1248127|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|$]]

Four spaces - it's what God uses.

blocks|key|1248146|text|雷·昂特科有一台Bibliography+of+Java+Coding+Standards。但是，很难将任何一项标准确定为“广泛采用”。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1248147|entityMap|0|LINK|mutability|MUTABLE|url|http://www.ontko.com/java/java_coding_standards.html^0|8|11|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

Ray Ontko has a <a href="http://www.ontko.com/java/java_coding_standards.html" rel="nofollow noreferrer">Bibliography of Java Coding Standards</a>. But it would be difficult to identify any single standard as "widely adopted".

blocks|key|1462910|text|您真正需要遵循的唯一编码标准是您的项目团队所接受的标准。您可能不同意使用制表符而不是空格，但如果这是您的团队的编码约定，您将尽最大努力遵循它。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1462911|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|$]]

The only coding standard you really need to follow is that as accepted by your project team. You might not agree with tabs instead of spaces, but if that is the coding convention of your team, you will do best to follow it.

blocks|key|1248231|text|BSD/Allman是唯一像样的缩进样式。它符合花括号的基本规则-如果它们位于不同的行，则它们应该位于同一列。与K&R相比，即使是Horstmann也是可以容忍的。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1248232|如果在记事本中编写代码，请始终使用大括号。否则，由于IDE的自动缩进特性，它是无用的，也是令人讨厌的。|1248233|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|$]]

BSD/Allman is the only decent indent style. It meets the basic rule of curly brackets - if they sit on different lines, they should sit on the same column. Even Horstmann is tolerable compared to K&amp;R.

Always put curly brackets if you code in notepad. Otherwise, due to the auto-indenting features of your IDE, it is useless and annoying.

blocks|key|1248250|text|检查Elements+of+Java+Style|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1248251|entityMap|0|LINK|mutability|MUTABLE|url|https://rads.stackoverflow.com/amzn/click/com/0521777682^0|2|M|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

Check <a href="https://rads.stackoverflow.com/amzn/click/com/0521777682" rel="nofollow noreferrer" rel="nofollow noreferrer">Elements of Java Style</a>

blocks|key|1248296|text|请考虑使用IDE的重新格式化程序机制缺省使用的格式化程序。从长远来看，这将为你节省大量时间。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1248297|我们在Eclipse和tick+Format+Source中启用了保存操作，因此源码总是被重新格式化。这意味着重新格式化只会更改自上次保存文件以来发生的事情。在源代码控制历史中是很好的。|1248298|您自然可以从容不迫地定义您自己的格式，但使用Eclipse标准往往会更容易-这对我们来说是可以的。|1248299|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|H|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|I|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|J|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|G|$]]

Consider using the one used by default by your IDE's reformatter mechanism. Will save you a lot of time in the long run.

We enable save actions in Eclipse and tick Format Source so the sources always are reformatted. This means that a reformat only changes things happened since last time the file was saved. Is nice in source control history.

You can naturally take your time and define your own format, but it tends to be easier just using the Eclipse standard - it is ok for us.

blocks|key|1463083|text|官方编码约定可在以下网址找到：http://www.oracle.com/technetwork/java/javase/documentation/codeconvtoc-136057.html|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1463084|entityMap|0|LINK|mutability|MUTABLE|url|http://www.oracle.com/technetwork/java/javase/documentation/codeconvtoc-136057.html^0|F|2B|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

Official coding conventions are found at this URL: <a href="http://www.oracle.com/technetwork/java/javase/documentation/codeconvtoc-136057.html" rel="nofollow">http://www.oracle.com/technetwork/java/javase/documentation/codeconvtoc-136057.html</a>

Sun's "<a href="http://java.sun.com/docs/codeconv/" rel="noreferrer">Code Conventions for the Java Programming Language</a>" was last updated April 1999. Ten years later a lot has changed in the language, as well as general usage patterns. Are there more up to date, widely adopted standards?

Most guidelines omit specifying file encoding and line endings. Sun recommends mixed tabs and spaces. The Eclipse IDE defaults to Eclipse's standard, which is tabs only. The <a href="http://maven.apache.org/developers/conventions/code.html" rel="noreferrer">Maven style guide</a> is spaces only. Many style guides, such as <a href="http://docs.jboss.org/process-guide/en/html/coding.html" rel="noreferrer">JBoss</a>, follow Sun's guidelines, but prefer K&amp;R braces instead of <a href="http://en.wikipedia.org/wiki/Indent_style#Variant:_1TBS" rel="noreferrer">OTBS</a>. Each Apache project has it's own style guide, with slight differences between each one.

Are there any widespread, modern Java coding conventions?

Eclipse

Sun的"“最近一次更新是在1999年4月。十年后，语言和一般使用模式都发生了很大变化。是否有更多最新的、被广泛采用的标准？大多数指南省略了指定文件编码和行尾。Sun建议混合使用制表符和空格。Eclipse IDE缺省为Eclipse的标准，仅为制表符。仅为空格。许多风格指南，如，遵循太阳公司的指南，但更喜欢K&R大括...

问是否有任何广泛的、现代的Java编码约定？
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问是否有任何广泛的、现代的Java编码约定？EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问是否有任何广泛的、现代的Java编码约定？
EN